Triple
T28563278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACE |
E722604
|
entity |
| Predicate | explorerNumber |
P167919
|
FINISHED |
| Object | Explorer 71 |
—
|
NE NERFINISHED |
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: Explorer 71 | Statement: [ACE, explorerNumber, Explorer 71]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explorerNumber Context triple: [ACE, explorerNumber, Explorer 71]
-
A.
explorer
Indicates that an entity engages in the activity of exploring or investigating places, ideas, or domains.
-
B.
explorerDesignation
Indicates that an entity has been assigned a specific role, title, or status as an explorer.
-
C.
explorerEditionReleaseDate
Indicates the date on which an explorer edition of a product or software is officially released.
-
D.
associatedExplorer
Indicates a relationship where one entity is linked to or connected with an explorer, typically signifying that the explorer is relevant to, involved with, or responsible for that entity in some context.
-
E.
explorerClass
Indicates that an entity belongs to, or is categorized within, a particular class or type of explorer.
- 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_69f01a5f69d08190ad5c0d2167078dec |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 4:06 a.m.