Triple
T37089502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIEFORE |
E918375
|
entity |
| Predicate | supervisionAbbreviation |
P178405
|
FINISHED |
| Object | SHCP |
—
|
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: SHCP | Statement: [SIEFORE, supervisionAbbreviation, SHCP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supervisionAbbreviation Context triple: [SIEFORE, supervisionAbbreviation, SHCP]
-
A.
governsOrganizationAbbreviation
Indicates that one entity has authoritative control or oversight over the use or assignment of an abbreviation that represents an organization.
-
B.
supervisionOf
Indicates that one entity oversees, directs, or manages the work, behavior, or activities of another entity.
-
C.
authorityAbbreviationFor
Indicates that one entity is an official abbreviated form or short designation used by an authority for another entity.
-
D.
monitoredByAbbreviation
chosen
Indicates that an entity is monitored or overseen by an organization, system, or authority referred to by its abbreviated name.
-
E.
refersToWorkTitleAbbreviationOf
Indicates that one entity refers to a work by using an abbreviated form of that work’s title.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:14 p.m.