Triple
T186758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Economic Committee of Congress |
E3997
|
entity |
| Predicate | hasHouseMembers |
P4273
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Joint Economic Committee of Congress, hasHouseMembers, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHouseMembers Context triple: [Joint Economic Committee of Congress, hasHouseMembers, 10]
-
A.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
B.
hasMajorityPartyMembers
Indicates that a group, body, or organization contains more members from a particular political party than from any other party, giving that party majority representation.
-
C.
hasCommittee
Indicates that an entity is associated with or overseen by a specific committee.
-
D.
hasElectoralRepresentation
Indicates that one entity is represented in an electoral body or decision-making institution by another entity (such as a representative, party, or delegation).
-
E.
numberOfRepresentatives
chosen
Indicates the quantity of representatives associated with a given entity or unit.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2594809288190b3d3b1283e7e0d00 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a25670feb081908e26a2543ebe7b3a |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.