Triple
T36169712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artemis Base Camp |
E1046112
|
entity |
| Predicate | plannedUsers |
P193157
|
FINISHED |
| Object | NASA astronauts |
—
|
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: NASA astronauts | Statement: [Artemis Base Camp, plannedUsers, NASA astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedUsers Context triple: [Artemis Base Camp, plannedUsers, NASA astronauts]
-
A.
plannedClients
Indicates that an entity has scheduled or intended clients associated with it, typically for future services or engagements.
-
B.
plannedWith
Indicates that an entity created or arranged a plan in collaboration or coordination with another entity.
-
C.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
D.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
E.
spanPlannedBy
Indicates that a time span or interval is scheduled, organized, or arranged by a particular agent or planner.
- 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_69f76e396bc88190b99d221bff9be27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:08 p.m.