Triple
T5451897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Universal Control |
E122388
|
entity |
| Predicate | continuityCategory |
P87
|
FINISHED |
| Object | input and control sharing |
—
|
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: input and control sharing | Statement: [Universal Control, continuityCategory, input and control sharing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuityCategory Context triple: [Universal Control, continuityCategory, input and control sharing]
-
A.
continuityFrom
Indicates that one entity continues, extends, or proceeds directly from another in a seamless or unbroken manner.
-
B.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
C.
symbolicContinuity
Indicates that there is a consistent, ongoing use or preservation of the same symbols or symbolic forms across time, contexts, or instances.
-
D.
partOfContinuum
Indicates that one entity exists as a segment or phase within a continuous sequence, range, or progression that includes the other entity.
-
E.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
- 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_69bd46424248819085282ddf50a565f3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd95be329c81908783420cf81b6af5 |
completed | March 20, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69bd919e8d18819098c4af6a015e5cc2 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:08 p.m.