Triple
T37720531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon |
E939569
|
entity |
| Predicate | firstISSVisitDate |
P27235
|
FINISHED |
| Object | 2012-05-25 |
—
|
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: 2012-05-25 | Statement: [Dragon, firstISSVisitDate, 2012-05-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstISSVisitDate Context triple: [Dragon, firstISSVisitDate, 2012-05-25]
-
A.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
B.
firstReachedDate
chosen
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
C.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
D.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
-
E.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.