Triple
T24764063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross expedition |
E619530
|
entity |
| Predicate | collectedDataOn |
P4241
|
FINISHED |
| Object | Earth’s magnetic field |
—
|
LITERAL FINISHED |
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: Earth’s magnetic field | Statement: [Ross expedition, collectedDataOn, Earth’s magnetic field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectedDataOn Context triple: [Ross expedition, collectedDataOn, Earth’s magnetic field]
-
A.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
-
B.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
C.
collectsInformationOn
Indicates that one entity gathers or acquires data, facts, or details about another entity.
-
D.
dataTypeCollected
chosen
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
E.
collectedWith
Indicates that one entity was gathered, acquired, or obtained together with another entity as part of the same collection event or process.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a4591c81909f918efd84a1f6f6 |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:28 a.m.