Triple
T3028175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo slaying Python |
E82829
|
entity |
| Predicate | PythonDescribedAs |
P45078
|
FINISHED |
| Object | serpent |
—
|
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: serpent | Statement: [Apollo slaying Python, PythonDescribedAs, serpent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PythonDescribedAs Context triple: [Apollo slaying Python, PythonDescribedAs, serpent]
-
A.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
B.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
C.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
D.
describes
Indicates that one entity provides an explanation, representation, or account of another entity or concept.
-
E.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
- 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_69ad8b21a62881908ec5dd4fba4a187c |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9abea8f4819090554d7319778170 |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961e2a408190afb1759132701305 |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad97ba55dc8190b6dddddfb751cf64 |
completed | March 8, 2026, 3:37 p.m. |
Created at: March 8, 2026, 3 p.m.