Triple
T31421685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evolver universe |
E801546
|
entity |
| Predicate | hasOntologyElement |
P129410
|
FINISHED |
| Object | character |
—
|
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: character | Statement: [Evolver universe, hasOntologyElement, character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOntologyElement Context triple: [Evolver universe, hasOntologyElement, character]
-
A.
hasAxiom
Indicates that an entity is associated with, defined by, or governed through a specific axiom or set of axioms.
-
B.
hasOntologicalCategory
chosen
Indicates that an entity belongs to, or is classified under, a specific ontological category or type within a conceptual framework.
-
C.
hasElementType
Indicates that something is composed of or contains elements that are of a specified type.
-
D.
hasAxiomSchema
Indicates that one entity is associated with, defined by, or governed through a particular axiom schema.
-
E.
hasLinguisticElement
Indicates that one entity includes, is associated with, or is characterized by a particular linguistic component such as a word, phrase, symbol, or other language element.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 8:48 p.m.