Triple
T33839912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Sample 15415 |
E867330
|
entity |
| Predicate | collectedFromLocation |
P139374
|
FINISHED |
| Object | Hadley-Apennine region of the Moon |
—
|
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: Hadley-Apennine region of the Moon | Statement: [Lunar Sample 15415, collectedFromLocation, Hadley-Apennine region of the Moon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedFromLocation Context triple: [Lunar Sample 15415, collectedFromLocation, Hadley-Apennine region of the Moon]
-
A.
retrievedFromLocation
chosen
Indicates that an entity was obtained, collected, or taken from a specified location.
-
B.
dataCollectionLocation
Indicates the place or setting where data is gathered, recorded, or measured.
-
C.
introducedFromLocation
Indicates that something or someone was brought, initiated, or first made present starting from a specified location.
-
D.
collectionOrigin
Indicates that one entity is the source, provenance, or originating context from which a collection of items or data has been derived or assembled.
-
E.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: May 1, 2026, 1:47 a.m.