Triple
T474691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Representative |
E9034
|
entity |
| Predicate | canServeOn |
P13463
|
FINISHED |
| Object | House committees |
—
|
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: House committees | Statement: [U.S. Representative, canServeOn, House committees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canServeOn Context triple: [U.S. Representative, canServeOn, House committees]
-
A.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
B.
servesUnder
Indicates that one entity works in a subordinate role under the authority, command, or supervision of another entity.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
servedByService
Indicates that something is provided, handled, or fulfilled by a particular service.
-
E.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f039f3d88190a7c93ecbf1bf5f58 |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edeed31881908cf43beed410572d |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeba8a488190986cc7381332f783 |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.