Triple
T28871391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AE |
E732153
|
entity |
| Predicate | roleInAssociation |
P110783
|
FINISHED |
| Object | SCU |
—
|
NE NERFINISHED |
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: SCU | Statement: [AE, roleInAssociation, SCU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAssociation Context triple: [AE, roleInAssociation, SCU]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
agencyRole
Indicates that one entity serves in a specific functional or organizational capacity on behalf of, or within, another entity (such as an agency, institution, or governing body).
-
C.
associatedCollectiveRole
chosen
Indicates that an entity is linked to a role or function held within a collective, group, or organization.
-
D.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or activity.
-
E.
collaboratorRole
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: April 28, 2026, 7:33 a.m.