Triple
T27732681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | System.Single |
E697466
|
entity |
| Predicate | isUnmanaged |
P163127
|
FINISHED |
| Object | True |
—
|
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: True | Statement: [System.Single, isUnmanaged, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnmanaged Context triple: [System.Single, isUnmanaged, True]
-
A.
isManaged
Indicates that one entity exercises supervisory or administrative control over another entity.
-
B.
isManagedFor
Indicates that one entity is administered, overseen, or controlled on behalf of another entity or purpose.
-
C.
isManagedWith
Indicates that one entity is administered, controlled, or operated using another entity as the managing tool, method, or resource.
-
D.
isFullyManaged
Indicates that one entity completely oversees, controls, and is responsible for managing another entity or process in all relevant aspects.
-
E.
notManagedBy
Indicates that an entity is explicitly not under the control, supervision, or administrative responsibility of the specified manager or managing entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6369e16a08190853fdd8ac05800f6 |
completed | May 2, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 3:12 p.m.