Triple
T9153509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOs |
E219647
|
entity |
| Predicate | stakeholderParticipation |
P1553
|
FINISHED |
| Object | governments |
—
|
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: governments | Statement: [SOs, stakeholderParticipation, governments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stakeholderParticipation Context triple: [SOs, stakeholderParticipation, governments]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
hasStakeholder
chosen
Indicates that an entity is a stakeholder of another entity, typically having an interest, involvement, or influence in its activities or outcomes.
-
C.
participationModel
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
D.
overseesParticipationOf
Indicates that one entity supervises, manages, or has authority over another entity’s involvement in an activity, process, or group.
-
E.
authorParticipation
Indicates that an author takes part in or contributes to a specific work, project, or publication.
- 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_69ca83e25418819093c6503deeaf30de |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96e323881909cbf4d6708f24f79 |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6605c6808190a30d92da006206ac |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.