Triple
T33839814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apennine Front |
E867327
|
entity |
| Predicate | wasSampledBy |
P57982
|
FINISHED |
| Object | Apollo 15 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: Apollo 15 astronauts | Statement: [Apennine Front, wasSampledBy, Apollo 15 astronauts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasSampledBy Context triple: [Apennine Front, wasSampledBy, Apollo 15 astronauts]
-
A.
hasBeenSampledIn
chosen
Indicates that an entity has been selected or taken as a sample within a specified context, location, or dataset.
-
B.
usesSamplingOf
Indicates that one entity employs or relies on a sample or subset derived from another entity for its operation, analysis, or processing.
-
C.
hasSampling
Indicates that one entity performs, involves, or is associated with the act or process of sampling in relation to another entity.
-
D.
workSampledBy
Indicates that a work (such as a song or recording) incorporates a portion of another work through sampling.
-
E.
basedOnSampleOf
Indicates that something is derived, inferred, or constructed from a particular sample or subset of data rather than from the entire population.
- 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_69f7004e55988190a2d35d4a95a34610 |
completed | May 3, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.