Triple
T26079375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Senate from Rhode Island |
E657787
|
entity |
| Predicate | isContinuousBody |
P49055
|
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: [United States Senate from Rhode Island, isContinuousBody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContinuousBody Context triple: [United States Senate from Rhode Island, isContinuousBody, true]
-
A.
isContinuous
Indicates that a function, process, or relationship changes smoothly without abrupt jumps or breaks over its domain.
-
B.
canBeContinuous
Indicates that something has the potential to occur, exist, or be maintained without interruption over a continuous range or period.
-
C.
isPermanentBody
chosen
Indicates that an entity functions as an enduring, officially established body or organization that is not temporary or ad hoc.
-
D.
hasBodyOf
Indicates that one entity possesses, contains, or is composed of the physical body or main substance of another entity.
-
E.
hasRepresentationContinuity
Indicates that one entity maintains a consistent or continuous representational relationship with another across time, context, or state changes.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 26, 2026, 7:36 p.m.