Triple
T35262052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Trianguli VI |
E1018393
|
entity |
| Predicate | governingComputer |
P203646
|
FINISHED |
| Object | Vaal |
—
|
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: Vaal | Statement: [Gamma Trianguli VI, governingComputer, Vaal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governingComputer Context triple: [Gamma Trianguli VI, governingComputer, Vaal]
-
A.
computerSystem
Indicates a relationship where an entity functions as or is classified as a computer system, typically comprising hardware, software, and related components that operate together.
-
B.
computingCenter
Indicates that an entity functions as or is associated with a computing center, i.e., a facility or unit where computing resources and services are provided or managed.
-
C.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
D.
primarySystem
Indicates that one system is designated as the main or most important system in relation to another system or context.
-
E.
hasOnboardComputer
Indicates that one entity is equipped with or contains an onboard computer system.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a01bcd39760819081807a02eb1939d1 |
completed | May 11, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_6a01bc3f1c74819087580e3134affc60 |
completed | May 11, 2026, 11:23 a.m. |
| PDg | Predicate description generation | batch_6a01bcd2d41081909176545b95bba88d |
completed | May 11, 2026, 11:26 a.m. |
Created at: May 3, 2026, 4:02 p.m.