Triple
T16171731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MultiFinder |
E392454
|
entity |
| Predicate | statusInSystem7 |
P121986
|
FINISHED |
| Object | always enabled |
—
|
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: always enabled | Statement: [MultiFinder, statusInSystem7, always enabled]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInSystem7 Context triple: [MultiFinder, statusInSystem7, always enabled]
-
A.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
B.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
C.
statusInSira
Indicates the status or standing that an entity holds within the Sira system or classification.
-
D.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
E.
statusInLogic
Indicates the logical status or role an entity holds within a formal reasoning or inference context.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb7ab1481908fc35bfc8c56e5f2 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.