Triple
T35574304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Signa Prime Selection |
E1028030
|
entity |
| Predicate | operatingActivity |
P70163
|
FINISHED |
| Object | owning properties |
—
|
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: owning properties | Statement: [Signa Prime Selection, operatingActivity, owning properties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatingActivity Context triple: [Signa Prime Selection, operatingActivity, owning properties]
-
A.
operateIn
Indicates that an entity performs its activities, functions, or services within a specified location, context, or domain.
-
B.
operationalNature
chosen
Indicates the functional or practical manner in which an entity, process, or system operates or carries out its activities.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
operatedAsset
Indicates that one entity is responsible for operating, managing, or running a particular asset.
-
E.
operatingCycle
Indicates the duration or process through which an entity completes a full sequence of its operations from start to finish.
- 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_69f76e0386688190b931bacdc145938c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0149447e448190b0480943de0691ee |
completed | May 11, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_6a0148e2c39c8190a3ad6ea6be902c04 |
completed | May 11, 2026, 3:11 a.m. |
Created at: May 3, 2026, 4:04 p.m.