Triple
T33839914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunar Sample 15415 |
E867330
|
entity |
| Predicate | collectedFromFeature |
P193560
|
FINISHED |
| Object | Apennine Front |
—
|
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: Apennine Front | Statement: [Lunar Sample 15415, collectedFromFeature, Apennine Front]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedFromFeature Context triple: [Lunar Sample 15415, collectedFromFeature, Apennine Front]
-
A.
featuresCollectionFrom
Indicates that one entity serves as the source or origin from which a collection of features is derived or obtained for another entity.
-
B.
collectedThrough
Indicates that something was obtained, gathered, or acquired by means of a specified process, method, or channel.
-
C.
collectedWith
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
-
D.
collectsFrom
Indicates that one entity gathers, receives, or takes something (such as items, data, or payments) from another entity.
-
E.
collectedAs
Indicates that one entity has been gathered, acquired, or assembled as part of another entity, such as a collection, set, or group.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd49f6dbac81909744373a357b7982 |
completed | May 8, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69fd48ed68f481908374183c66a6b055 |
completed | May 8, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69fd49f612a4819096fe7d5a3bb439ba |
completed | May 8, 2026, 2:27 a.m. |
Created at: May 1, 2026, 1:47 a.m.