Triple
T29723436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AO3 |
E752118
|
entity |
| Predicate | creationAnnounced |
P194988
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [AO3, creationAnnounced, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creationAnnounced Context triple: [AO3, creationAnnounced, 2007]
-
A.
creationResult
Indicates that one entity is the outcome or product that comes into existence as a result of another entity’s act of creation.
-
B.
placeCreated
Indicates that one entity is the location where another entity was created or came into existence.
-
C.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
D.
createdAround
Indicates that something was brought into existence or produced approximately at a particular time or within an imprecise time period.
-
E.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 28, 2026, 7:37 p.m.