Triple
T29669167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alvin |
E750616
|
entity |
| Predicate | firstTitanicExploration |
P123861
|
FINISHED |
| Object | 1986 |
—
|
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: 1986 | Statement: [Alvin, firstTitanicExploration, 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstTitanicExploration Context triple: [Alvin, firstTitanicExploration, 1986]
-
A.
firstMajorExplorationIn
Indicates that an entity represents the earliest significant exploration activity that took place in a specified location or context.
-
B.
firstMajorScientificExploration
chosen
Indicates that an entity represents the earliest significant scientific investigation or expedition undertaken by another entity.
-
C.
earlyExplorer
Indicates that an entity explored or investigated a place, field, or subject significantly earlier than most others.
-
D.
firstMajorDiscovery
Indicates that the object is the earliest significant discovery or breakthrough associated with the subject.
-
E.
firstToLand
Indicates that the subject is the earliest or initial entity to arrive at or touch down on a particular place or surface.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0120f070b081909b6d1a3d8ee6b80e |
completed | May 11, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_6a01209da37481909683e38f264b15ef |
completed | May 11, 2026, 12:19 a.m. |
Created at: April 28, 2026, 7:03 p.m.