Triple
T2278454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Legal Affairs |
E51225
|
entity |
| Predicate | isStandingBody |
P36525
|
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: [Committee on Legal Affairs, isStandingBody, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isStandingBody Context triple: [Committee on Legal Affairs, isStandingBody, true]
-
A.
hasStand
Indicates that an entity possesses, is equipped with, or is supported by a stand or base structure.
-
B.
hasStandsType
Indicates that an entity has or is associated with a particular type or category of stands (e.g., display stands, support stands, or similar structures).
-
C.
isFreeStanding
Indicates that an object or structure stands independently without needing external support or attachment.
-
D.
hasFightingStance
Indicates that an entity adopts or is characterized by a particular combat or fighting posture.
-
E.
hasStandsOn
Indicates that one entity is physically supported by and in contact with the upper surface of another entity.
- F. None of above. chosen
Provenance (4 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_69a88b08e4308190bdac9aebcca1c91a |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc217b6648190be77d2176d322efd |
completed | March 7, 2026, 6:13 a.m. |
| PD | Predicate disambiguation | batch_69abbdb9aa3c819088d0316c5269a1c2 |
completed | March 7, 2026, 5:55 a.m. |
| PDg | Predicate description generation | batch_69abbe4252688190944491a450383450 |
completed | March 7, 2026, 5:57 a.m. |
Created at: March 4, 2026, 7:48 p.m.