Triple
T33839813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apennine Front |
E867327
|
entity |
| Predicate | wasExploredDuring |
P23375
|
FINISHED |
| Object | Apollo 15 mission |
—
|
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 mission | Statement: [Apennine Front, wasExploredDuring, Apollo 15 mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasExploredDuring Context triple: [Apennine Front, wasExploredDuring, Apollo 15 mission]
-
A.
exploredDuring
chosen
Indicates that an entity was explored or investigated within the time frame or context of a specified event or period.
-
B.
isExploredThrough
Indicates that something is examined, investigated, or understood by means of a particular method, process, or medium.
-
C.
exploredWith
Indicates that one entity explored something together with another entity as companions or partners in the exploration.
-
D.
willBeExploredBy
Indicates that something is expected or planned to be examined, investigated, or studied by a particular agent in the future.
-
E.
visitedFor
Indicates that one entity traveled to or attended another entity (such as a place, person, or event) for a specific purpose or reason.
- 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_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:47 a.m.