Triple
T16940123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abó |
E410928
|
entity |
| Predicate | eraOfMissionActivity |
P125319
|
FINISHED |
| Object | early 1600s |
—
|
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: early 1600s | Statement: [Abó, eraOfMissionActivity, early 1600s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfMissionActivity Context triple: [Abó, eraOfMissionActivity, early 1600s]
-
A.
typeOfMission
Indicates the specific category or nature of a mission that an entity is associated with or engaged in.
-
B.
partOfMission
Indicates that one entity is a component, phase, or element belonging to or included within a larger mission.
-
C.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
D.
intendedMission
Indicates that one entity is the planned or designated mission, task, or objective associated with another entity.
-
E.
segmentMission
Indicates that a specific mission is associated with, assigned to, or carried out within a particular segment or phase.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cfacdbc48190988ac259712bb9e8 |
completed | April 18, 2026, 6:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b9aa8748190b248890aca86753d |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e355722040819098830dabf207ecd6 |
completed | April 18, 2026, 9:57 a.m. |
Created at: April 10, 2026, 5:31 a.m.