Triple
T338940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At-Large Advisory Committee |
E6789
|
entity |
| Predicate | participationModel |
P11584
|
FINISHED |
| Object | Bottom-up |
—
|
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: Bottom-up | Statement: [At-Large Advisory Committee, participationModel, Bottom-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participationModel Context triple: [At-Large Advisory Committee, participationModel, Bottom-up]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
regulatesParticipationIn
Indicates that one entity controls, directs, or sets rules governing another entity’s involvement in an activity, process, or system.
-
C.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
D.
hasParticipants
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
E.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea09a5e881908b313cb37409a4f9 |
completed | Feb. 28, 2026, 1:13 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.