Triple
T35994702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southwest Ordinance |
E1040947
|
entity |
| Predicate | appliedToFutureState |
P75171
|
FINISHED |
| Object | Tennessee |
—
|
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: Tennessee | Statement: [Southwest Ordinance, appliedToFutureState, Tennessee]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToFutureState Context triple: [Southwest Ordinance, appliedToFutureState, Tennessee]
-
A.
appliesToFutureEntity
Indicates that the relationship or action is directed toward or relevant for an entity that will exist or be realized in the future.
-
B.
appliesToSuccessorState
chosen
Indicates that the relationship or condition holds not in the current state but in the immediately following (successor) state of the system or process.
-
C.
appliedToStatesThrough
Indicates that something (such as a rule, policy, or process) is implemented or enforced by means of, or via the mediation of, particular states.
-
D.
appliesToAfter
Indicates that one entity becomes relevant or applicable only after another specified event, condition, or time has occurred.
-
E.
appliedBefore
Indicates that one action, process, or condition was applied earlier in time than 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_69f76e29084c819083987b828d414de7 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:07 p.m.