Triple
T6991551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-8 |
E162096
|
entity |
| Predicate | selfSynchronizing |
P34879
|
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: [UTF-8, selfSynchronizing, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selfSynchronizing Context triple: [UTF-8, selfSynchronizing, true]
-
A.
isSelfSynchronizing
chosen
Indicates that a process, system, or component can automatically align its timing or state with others without requiring external coordination or control.
-
B.
synchronizesWith
Indicates that two or more entities coordinate their states or activities so that they occur in step or remain temporally consistent with each other.
-
C.
selfGoverning
Indicates that an entity has the authority and capacity to govern, regulate, and manage itself independently, without external control.
-
D.
autonomousFor
Indicates that one entity operates or makes decisions independently on behalf of, or in place of, another specified context, system, or agent.
-
E.
selfPropelled
Indicates that an entity moves or operates by its own internal power or mechanism, without needing an external force to propel it.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.