Triple
T23317894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aldebaran B |
E590759
|
entity |
| Predicate | hasDetectionConfidence |
P36359
|
FINISHED |
| Object | tentative |
—
|
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: tentative | Statement: [Aldebaran B, hasDetectionConfidence, tentative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDetectionConfidence Context triple: [Aldebaran B, hasDetectionConfidence, tentative]
-
A.
hasCertainty
chosen
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
B.
errorDetectionCapability
Indicates the ability of an entity to detect the presence of errors in data, processes, or operations.
-
C.
detected
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
D.
findsConfidenceAt
Indicates that an entity gains or experiences a sense of confidence in relation to a particular context, source, or location.
-
E.
requiresConfidenceOf
Indicates that one entity can only proceed, function, or be accepted if it has sufficient trust, assurance, or belief in the reliability or correctness of 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197828c408190ae071624e40de4cc |
completed | April 29, 2026, 5:30 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:07 p.m.