Triple
T27879252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bound for Glory |
E705041
|
entity |
| Predicate | regionHeld |
P74939
|
FINISHED |
| Object | North America |
—
|
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: North America | Statement: [Bound for Glory, regionHeld, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionHeld Context triple: [Bound for Glory, regionHeld, North America]
-
A.
occupiedRegion
chosen
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
B.
regionAtStake
Indicates that a specific geographic or political area is the subject of contention, risk, or negotiation within a given situation or interaction.
-
C.
regionRuled
Indicates that a particular region is governed or controlled by a specified ruler or authority.
-
D.
regionLocking
Indicates that access to or use of something is restricted based on the geographic region of the user or device.
-
E.
hasRegion
Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 27, 2026, 6:29 p.m.