Triple
T22782187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M96 Group |
E563869
|
entity |
| Predicate | locatedInConstellation |
P40
|
FINISHED |
| Object | Leo |
—
|
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: Leo | Statement: [M96 Group, locatedInConstellation, Leo]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leo Context triple: [M96 Group, locatedInConstellation, Leo]
-
A.
Leo
chosen
Leo is a zodiac constellation and astrological sign traditionally associated with the lion, symbolizing courage, leadership, and creativity.
-
B.
Leo
Leo was the given name of Leo V of Armenia, the last king of the Armenian Kingdom of Cilicia in the late 14th century.
-
C.
Leo
Leo is a central character in Noël Coward’s sophisticated stage comedy "Design for Living," embodying the play’s themes of unconventional relationships and bohemian lifestyle.
-
D.
Leo
Leo is the regnal name of Leo IV the Khazar, a Byzantine emperor of the 8th century.
-
E.
Leo
Leo is a central character in the wuxia film "House of Flying Daggers," known for his complex loyalties and pivotal role in the story’s romantic and political intrigue.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2dd250819093a5c49806916ec4 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 3:28 p.m.