Triple
T30594958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Brown’s Provisional Constitution |
E778758
|
entity |
| Predicate | envisionedTerritory |
P24003
|
FINISHED |
| Object | United States |
—
|
NE NERFINISHED |
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: United States | Statement: [John Brown’s Provisional Constitution, envisionedTerritory, United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: envisionedTerritory Context triple: [John Brown’s Provisional Constitution, envisionedTerritory, United States]
-
A.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
B.
territorialAmbition
chosen
Indicates a desire or intent by one entity to expand its control, ownership, or influence over additional geographic areas or territories.
-
C.
laterTerritory
Indicates that one territory is a subsequent or successor territory to another in time.
-
D.
plannedArea
Indicates that an area is designated or intended for a specific planned use or development.
-
E.
territorialExtent
Indicates the geographic area or spatial range over which something extends, applies, or has jurisdiction.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6897e61408190add6f4bd2ffa4f84 |
completed | May 2, 2026, 11:32 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:24 p.m.