Triple
T23736720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLONASS Time |
E586558
|
entity |
| Predicate | maintainedIndependentlyFrom |
P153472
|
FINISHED |
| Object | UTC |
—
|
NE NERFINISHED |
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: UTC | Statement: [GLONASS Time, maintainedIndependentlyFrom, UTC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainedIndependentlyFrom Context triple: [GLONASS Time, maintainedIndependentlyFrom, UTC]
-
A.
worksIndependentlyOf
Indicates that one entity performs its function or activity without relying on, being influenced by, or requiring coordination with another entity.
-
B.
organizedIndependentlyOf
Indicates that an entity was organized or formed without direction, control, or coordination from another specified entity.
-
C.
hasIndependent
Indicates that one entity exists, functions, or operates without being controlled, influenced, or determined by another entity.
-
D.
hasIndependentCodeBaseFrom
Indicates that two software systems or components are developed and maintained using separate, non-shared code bases.
-
E.
independentlyDevelopedBy
Indicates that something was created or developed by an entity without collaboration, influence, or shared effort with others.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad28fa481909d7a6a6e98a7b0a5 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:10 p.m.