Triple
T5562980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castor |
E145808
|
entity |
| Predicate | SOIUSASectionCode |
P64503
|
FINISHED |
| Object | I/B-9 |
—
|
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: I/B-9 | Statement: [Castor, SOIUSASectionCode, I/B-9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SOIUSASectionCode Context triple: [Castor, SOIUSASectionCode, I/B-9]
-
A.
sectorCode
Indicates the classification code that identifies the economic or organizational sector associated with an entity or activity.
-
B.
codeForSovereignState
Indicates that an entity serves as a code or coded identifier that officially represents a particular sovereign state.
-
C.
SICCode
Indicates the standardized industrial classification code that categorizes the primary type of economic activity associated with an entity or relationship.
-
D.
IOCCode
Indicates the standardized three-letter country or territory code assigned by the International Olympic Committee to represent a National Olympic Committee in Olympic contexts.
-
E.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201ba0e88190acd5bfaa5973f2d8 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:36 p.m.