Triple
T30663840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rougarou |
E780603
|
entity |
| Predicate | openingDateAsMantis |
P180345
|
FINISHED |
| Object | 1996 |
—
|
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: 1996 | Statement: [Rougarou, openingDateAsMantis, 1996]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateAsMantis Context triple: [Rougarou, openingDateAsMantis, 1996]
-
A.
openedAt
Indicates that an entity began operating, became accessible, or was first made available at a specific time or date.
-
B.
rerAOpeningDate
Indicates the date on which something (such as a facility, service, or route) is opened again after having been closed.
-
C.
openingDateAsThroughLine
Indicates that the opening date is used as a continuous reference or organizing thread linking related events, records, or states over time.
-
D.
openingDateLine15
Indicates the date on which line 15 (e.g., a specific route, service, or infrastructure segment) was officially opened or began operation.
-
E.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
- 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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
| PDg | Predicate description generation | batch_69f73adfd9a081908adae6bd59dfefb9 |
completed | May 3, 2026, 12:09 p.m. |
Created at: April 29, 2026, 8:31 p.m.