Triple
T16133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Congress |
E321
|
entity |
| Predicate | hasTermLength |
P540
|
FINISHED |
| Object | 2 years for each Congress |
—
|
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: 2 years for each Congress | Statement: [United States Congress, hasTermLength, 2 years for each Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTermLength Context triple: [United States Congress, hasTermLength, 2 years for each Congress]
-
A.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
termLimitDefinedBy
Indicates that the duration or number of terms for holding a position is specified or constrained by a particular rule, law, or authority.
-
C.
length
Indicates a measurement relationship where a value specifies how long something is from one end to the other.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
hasLimitation
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
- 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_69a23d7ad88c8190bffe8ab091d86642 |
completed | Feb. 28, 2026, 12:57 a.m. |
| NER | Named-entity recognition | batch_69a241ea1ea081908e8a81ca97531ba5 |
completed | Feb. 28, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69a23fec1fe8819080da6f2c745dc8fd |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 1:02 a.m.