Triple
T20716049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty (Klingon Bird-of-Prey) |
E509171
|
entity |
| Predicate | visitedTimePeriod |
P26942
|
FINISHED |
| Object | late 20th-century Earth |
—
|
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: late 20th-century Earth | Statement: [HMS Bounty (Klingon Bird-of-Prey), visitedTimePeriod, late 20th-century Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visitedTimePeriod Context triple: [HMS Bounty (Klingon Bird-of-Prey), visitedTimePeriod, late 20th-century Earth]
-
A.
locationPeriod
Indicates that an entity is associated with being at a particular location during a specified time period.
-
B.
visitedDate
Indicates the specific date on which one entity visited or was present at another entity or location.
-
C.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
D.
visitedDuring
chosen
Indicates that one entity was present at or traveled to another entity within a specified time period or event.
-
E.
showsTimePeriod
Indicates that one entity presents or displays a specific span or interval of time associated with another entity.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1d1f3308190ae594a5b9e4ab9d5 |
completed | April 21, 2026, 12:16 a.m. |
| PD | Predicate disambiguation | batch_69e5c04b31248190b9b9d91b5cb854e3 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:15 p.m.