Triple
T38067129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trojan |
E950499
|
entity |
| Predicate | notablePrince |
—
|
GENERATED |
| Object | Hector |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePrince Context triple: [Trojan, notablePrince, Hector]
-
A.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
notableSoul
Indicates that a person is recognized for having a distinguished or remarkable soul, character, or inner spiritual quality.
-
C.
notableDuo
Indicates that two entities are widely recognized together as a famous or significant pair.
-
D.
notableSingle
Indicates that the subject is particularly recognized or distinguished for one specific, individual instance (such as a single work, event, or achievement).
-
E.
notablePrime
Indicates that a number is a prime with special significance or prominence (for example, due to unique properties, historical importance, or frequent use).
- F. None of above. chosen
Provenance (1 batch)
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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:21 p.m.