Triple
T11437126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primary Reference Time Clock |
E271038
|
entity |
| Predicate | mayBeDerivedFrom |
P909
|
FINISHED |
| Object | GNSS receiver |
—
|
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: GNSS receiver | Statement: [Primary Reference Time Clock, mayBeDerivedFrom, GNSS receiver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayBeDerivedFrom Context triple: [Primary Reference Time Clock, mayBeDerivedFrom, GNSS receiver]
-
A.
derivedFrom
chosen
Indicates that one entity originates, is obtained, or is developed from another source entity.
-
B.
isDerivedFromGivenName
Indicates that one entity originates from, or is formed based on, a specified given (first) name.
-
C.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
-
D.
isBaseFor
Indicates that one entity serves as the foundational support, starting point, or underlying basis upon which another entity is built, developed, or depends.
-
E.
notDerivedFrom
Indicates that one entity is explicitly not obtained, inferred, or produced from 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8088711ec8190afae9f4d9f2a11ca |
completed | April 9, 2026, 8:13 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.