Triple
T34643518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | firstVisitedByHumansDate |
P205500
|
FINISHED |
| Object | 1969-11-19 |
—
|
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: 1969-11-19 | Statement: [Surveyor 3 landing site, firstVisitedByHumansDate, 1969-11-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstVisitedByHumansDate Context triple: [Surveyor 3 landing site, firstVisitedByHumansDate, 1969-11-19]
-
A.
firstAppearedOnGlobeBy
Indicates that an entity made its first appearance or was first featured on a globe created or authored by the specified source.
-
B.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
C.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
D.
firstContactWithHumans
Indicates that the subject entity is the first to establish contact or interaction with humans.
-
E.
firstChartedOn
Indicates that an entity was first mapped, recorded, or charted on a specific date or during a specific time.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:04 a.m.