Triple
T13460371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Colony |
E311346
|
entity |
| Predicate | selectionCriteriaForSettlers |
P109589
|
FINISHED |
| Object | moral character |
—
|
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: moral character | Statement: [Union Colony, selectionCriteriaForSettlers, moral character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectionCriteriaForSettlers Context triple: [Union Colony, selectionCriteriaForSettlers, moral character]
-
A.
settlerType
Indicates the specific category or classification of a settler involved in the relationship or context.
-
B.
settlerOf
Indicates that an entity established or inhabited a place as a settler of that location.
-
C.
numberOfInitialSettlers
Indicates the quantity of settlers present at the initial establishment of a settlement or colony.
-
D.
mainSettlement
Indicates that one settlement serves as the primary or most important settlement associated with a given area, region, or administrative unit.
-
E.
foundingRulerInvitingSettlement
Indicates that a founding ruler initiates or invites the establishment of a new settlement or community.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0c177081909178dec61b09c278 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03dcd0c8190a8927eb4eaad1c45 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadce235f88190a6433395d2969811 |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:41 p.m.