Triple
T34071481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NGC 7174 |
E873779
|
entity |
| Predicate | hasNearbyCompanion |
P39585
|
FINISHED |
| Object | NGC 7172 |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: NGC 7172 | Statement: [NGC 7174, hasNearbyCompanion, NGC 7172]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyCompanion Context triple: [NGC 7174, hasNearbyCompanion, NGC 7172]
-
A.
hasNearbyPassage
Indicates that one location or object is situated close to a passage, such as a corridor, tunnel, or route, that provides access or transit nearby.
-
B.
hasNotableNearbyEntity
chosen
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
-
C.
companionOf
Indicates that one entity serves as a companion or partner to another, typically accompanying or being closely associated with them.
-
D.
hasCompanionInGroup
Indicates that an entity is accompanied by or associated with at least one other entity within the same group or collective context.
-
E.
hasCompanionColleague
Indicates that one entity has another entity as a colleague who also serves as a companion or close associate.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ffaa7bc45c8190b907db8579244a7b |
completed | May 9, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69ffa9f6c9a481908fbd4d18b311cbe2 |
completed | May 9, 2026, 9:41 p.m. |
Created at: May 1, 2026, 1:52 a.m.