Triple
T24265055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OBX Index |
E604815
|
entity |
| Predicate | hasComponents |
P25619
|
FINISHED |
| Object | large Norwegian listed companies |
—
|
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: large Norwegian listed companies | Statement: [OBX Index, hasComponents, large Norwegian listed companies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponents Context triple: [OBX Index, hasComponents, large Norwegian listed companies]
-
A.
hasSubcomponent
chosen
Indicates that one entity is a constituent part or component of another, larger entity.
-
B.
hasComponentCount
Indicates that an entity is associated with a specific number of components it contains or comprises.
-
C.
hasComponentGroup
Indicates that an entity includes or is associated with a specific group of components treated as a single unit.
-
D.
hasComponentForm
Indicates that one entity exists as a structural or compositional form or variant of another entity.
-
E.
hasComponentModel
Indicates that an entity includes or is associated with a specific component model as part of its structure or configuration.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28c6b32108190856be036ac9cfced |
completed | April 29, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:06 a.m.