Triple
T7004536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassiphone |
E162419
|
entity |
| Predicate | ontologyClass |
P39732
|
FINISHED |
| Object | mythologicalPerson |
—
|
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: mythologicalPerson | Statement: [Cassiphone, ontologyClass, mythologicalPerson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ontologyClass Context triple: [Cassiphone, ontologyClass, mythologicalPerson]
-
A.
ontologyId
Indicates that there is an association between an entity and a specific ontology identifier that formally defines or classifies it within an ontology.
-
B.
ontologyStatus
Indicates the current state or condition of an entity within an ontology lifecycle (e.g., proposed, active, deprecated, or obsolete).
-
C.
protégéOf
Indicates that one entity is mentored, trained, or guided in their development by another, more experienced entity.
-
D.
classificationTerm
chosen
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
E.
EUTaxonomy
Indicates that something is classified or evaluated according to the EU Taxonomy framework for environmentally sustainable economic activities.
- F. None of above.
Provenance (3 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_69c6885928148190ae31909fbb5e9849 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dc14037c81908bb87250ef29be50 |
completed | March 27, 2026, 7:35 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c67c94819084fdcf0398606027 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:33 p.m.