Triple
T34046369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phanes |
E873097
|
entity |
| Predicate | broughtIntoExistence |
P178012
|
FINISHED |
| Object | universe |
—
|
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: universe | Statement: [Phanes, broughtIntoExistence, universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broughtIntoExistence Context triple: [Phanes, broughtIntoExistence, universe]
-
A.
createdBeingFrom
chosen
Indicates that one entity brought another entity into existence or produced it as a result of its creative action.
-
B.
broughtBack
Indicates that an entity caused another entity to return to a previous place, state, or condition.
-
C.
createdByConstructionOf
Indicates that something comes into existence as a result of a construction process or building activity performed by an agent.
-
D.
proposesExistenceOf
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
-
E.
broughtOn
Indicates that one entity caused, initiated, or was responsible for the occurrence or introduction of another entity or event.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.