Triple
T34643549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | analysisConductedAt |
P179561
|
FINISHED |
| Object | NASA laboratories on 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: NASA laboratories on Earth | Statement: [Surveyor 3 landing site, analysisConductedAt, NASA laboratories on Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: analysisConductedAt Context triple: [Surveyor 3 landing site, analysisConductedAt, NASA laboratories on Earth]
-
A.
analysisMode
Indicates that an entity is operating under a specific analytical configuration or method for processing or evaluating information.
-
B.
timePeriodAnalyzed
Indicates that a specified time period is the focus or scope of an analysis or evaluation.
-
C.
hasAnalysis
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
D.
conductedOn
Indicates that an action, process, or event was carried out with respect to, or took place on, a specified subject, object, or medium.
-
E.
updatesAnalysisOf
Indicates that one entity revises, refines, or replaces the existing analysis associated with another entity.
- 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_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.