Triple
T36354747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 237 |
E895307
|
entity |
| Predicate | isNumberReusedInMultipleStates |
P91997
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SR 237, isNumberReusedInMultipleStates, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNumberReusedInMultipleStates Context triple: [SR 237, isNumberReusedInMultipleStates, true]
-
A.
isReuseOf
Indicates that one entity is derived from, or created by reusing, the content, structure, or components of another entity.
-
B.
isNumberedWithinState
Indicates that an entity has an assigned number that is unique or valid only within the context or boundaries of a particular state.
-
C.
isMultiState
Indicates that the entity exists or operates in more than one distinct state or condition.
-
D.
reusedIn
chosen
Indicates that something previously used in one context or instance is used again in another context or instance.
-
E.
previouslyUsedNumberDesignationsUntil
Indicates that certain number designations were used for an entity up until a specified point in time, after which they were no longer in use.
- 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_69f76e4f437c8190a1af3ea2564f41f5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:09 p.m.