Triple
T38428506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Wise |
E903729
|
entity |
| Predicate | treatyCharacterization |
P20718
|
FINISHED |
| Object | controversial treaty |
—
|
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: controversial treaty | Statement: [Fort Wise, treatyCharacterization, controversial treaty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatyCharacterization Context triple: [Fort Wise, treatyCharacterization, controversial treaty]
-
A.
treatyType
chosen
Indicates the specific category or classification of a treaty that characterizes the nature of the agreement between parties.
-
B.
treaty
Indicates a formal, negotiated agreement or pact established between entities, typically states or organizations, that defines mutual obligations, rights, or terms of cooperation.
-
C.
treatyReviewed
Indicates that a treaty has been examined and evaluated, typically for its terms, implications, or compliance, by an authorized party.
-
D.
treatyFeature
Indicates that one entity is a characteristic, provision, or specific element that forms part of a treaty.
-
E.
treatyFamily
Indicates that there exists a familial or kinship-based treaty or formal agreement relationship between the entities.
- 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_69f76e6a2024819081aa04f4932f89d2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: May 3, 2026, 4:31 p.m.