Triple
T28388409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIS II |
E719084
|
entity |
| Predicate | centralSystemName |
P55846
|
FINISHED |
| Object | Central SIS II (C.SIS II) |
—
|
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: Central SIS II (C.SIS II) | Statement: [SIS II, centralSystemName, Central SIS II (C.SIS II)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSystemName Context triple: [SIS II, centralSystemName, Central SIS II (C.SIS II)]
-
A.
centralName
Indicates that the specified name serves as the primary or main identifying label within a given context or naming structure.
-
B.
systemName
chosen
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
C.
centralResource
Indicates that one entity functions as the primary or core resource upon which another entity depends or is organized.
-
D.
centralEntity
Indicates that the subject serves as the primary or most important entity around which related entities, actions, or information are organized.
-
E.
chieflySystem
Indicates that something serves primarily or predominantly as a system, or that its main role or function is system-related.
- 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_69eff6ef211081909d31d9be5f5567e6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 28, 2026, 1:11 a.m.