Triple
T24417899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marquesans |
E615636
|
entity |
| Predicate | colonizedInCentury |
P155853
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Marquesans, colonizedInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colonizedInCentury Context triple: [Marquesans, colonizedInCentury, 19th century]
-
A.
colonizationStartYear
Indicates the year in which a process of colonization of a place or territory began.
-
B.
settledInCentury
Indicates that an entity’s act of settling or establishment occurred during a specified century.
-
C.
hasColonialEraInteractionWith
Indicates a relationship in which two entities were involved with each other during the colonial era, such as through governance, trade, conflict, or other forms of interaction tied to colonial rule.
-
D.
regionOfColonization
Indicates the geographic area or territory where a colonizing entity establishes and exercises colonial control.
-
E.
administeredColonyInCentury
Indicates that a governing entity administered control over a colony during a specified century.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29587b2308190907886b82d8c5129 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:13 a.m.