Triple
T5112724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dynasties |
E115254
|
entity |
| Predicate | hasEpisodeAbout |
P61669
|
FINISHED |
| Object | chimpanzees |
—
|
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: chimpanzees | Statement: [Dynasties, hasEpisodeAbout, chimpanzees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpisodeAbout Context triple: [Dynasties, hasEpisodeAbout, chimpanzees]
-
A.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
-
B.
hasEP
Indicates that an entity possesses, is associated with, or is characterized by a specific EP (e.g., an endpoint, event point, or designated EP resource) in the given context.
-
C.
associatedEpisode
Indicates that one entity is linked or connected to a particular episode as its related or relevant installment.
-
D.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
E.
hasMissingEpisode
Indicates that an entity (such as a series or season) is associated with one or more episodes that are absent or not available.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75cba1e88190af076657f846b975 |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.