Triple
T21580097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State of Franklin |
E532499
|
entity |
| Predicate | aspiredStatus |
P13062
|
FINISHED |
| Object | fourteenth U.S. state |
—
|
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: fourteenth U.S. state | Statement: [State of Franklin, aspiredStatus, fourteenth U.S. state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aspiredStatus Context triple: [State of Franklin, aspiredStatus, fourteenth U.S. state]
-
A.
seeksStatusAs
chosen
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
B.
advancementStatus
Indicates the current stage or progress state of an ongoing process, project, or development.
-
C.
statusUnderASC
Indicates that one entity has a particular accounting or reporting status as defined under ASC (Accounting Standards Codification) relative to another context or framework.
-
D.
awardedStatus
Indicates that a particular status, honor, or designation has been formally granted to an entity.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
- 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_69e0c4618bec8190bcb0feb74568cbb1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeeb5b8118819095fd751a03fbe8e8 |
completed | April 27, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:31 p.m.