Triple
T206470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon |
E4619
|
entity |
| Predicate | hasBeenVisitedByHumans |
P1096
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Moon, hasBeenVisitedByHumans, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenVisitedByHumans Context triple: [Moon, hasBeenVisitedByHumans, true]
-
A.
visitedBy
chosen
Indicates that a location or entity is the destination or target of a visit performed by another entity.
-
B.
hasHistoricSite
Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
-
C.
historicallyInhabitedBy
Indicates that a place or region was inhabited by a particular group or population during some period in the past.
-
D.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
E.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.