Triple
T156660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeus |
E3194
|
entity |
| Predicate | led |
P6947
|
FINISHED |
| Object | Olympian gods in Titanomachy |
—
|
LITERAL FINISHED |
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: Olympian gods in Titanomachy | Statement: [Zeus, led, Olympian gods in Titanomachy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: led Context triple: [Zeus, led, Olympian gods in Titanomachy]
-
A.
ledExpedition
Indicates that one entity organized and directed an expedition involving another entity or group.
-
B.
ledLeagueIn
Indicates that an entity achieved the highest performance or total in a specified statistical category within a particular league for a given season or time period.
-
C.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
D.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
E.
lays
Indicates that one entity deposits or places something, typically eggs or objects, onto a surface or in a location.
- F. None of above. chosen
Provenance (4 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a258808ff08190a06b6206f635612b |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2565ded588190a27319aaa0130b4f |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2587f1fe48190b1235aa63448fec5 |
completed | Feb. 28, 2026, 2:52 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.