Triple
T31493595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Florida Treaty |
E803476
|
entity |
| Predicate | relatedToPolicyOf |
P48852
|
FINISHED |
| Object | U.S. expansionism |
—
|
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: U.S. expansionism | Statement: [Florida Treaty, relatedToPolicyOf, U.S. expansionism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToPolicyOf Context triple: [Florida Treaty, relatedToPolicyOf, U.S. expansionism]
-
A.
linkedToPolicy
chosen
Indicates that an entity is associated or connected to a specific policy, such that the policy governs, influences, or is relevant to that entity.
-
B.
associatedPolis
Indicates a relationship where an entity is linked or connected to a particular city-state (polis), typically as its relevant or related political unit.
-
C.
relatedTo
Indicates a general, non-specific relationship or association exists between two entities.
-
D.
relatedToClaimOf
Indicates a relationship where something is connected or pertinent to a specific claim or assertion.
-
E.
relatedToTerm
Indicates a general, non-specific relationship or association between one term and another.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:39 p.m.