Triple
T14809908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M982 Excalibur |
E348150
|
entity |
| Predicate | circularErrorProbable |
P115816
|
FINISHED |
| Object | about 5 meters |
—
|
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: about 5 meters | Statement: [M982 Excalibur, circularErrorProbable, about 5 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circularErrorProbable Context triple: [M982 Excalibur, circularErrorProbable, about 5 meters]
-
A.
hasFailureProbability
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
B.
hasCircle
Indicates that one entity possesses, contains, or includes a circle as part of its structure or composition.
-
C.
numberOfProbableCases
Indicates the quantified count of cases that are considered likely or suspected to occur or have occurred, based on available evidence or criteria.
-
D.
isOnCircularRoute
Indicates that an entity follows or belongs to a route that forms a closed loop, starting and ending at the same point.
-
E.
circumventedBy
Indicates that an intended rule, obstacle, or control is avoided, bypassed, or rendered ineffective through the actions or methods of another entity.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decf35a5e081909321193ef37099d1 |
completed | April 14, 2026, 11:35 p.m. |
| PD | Predicate disambiguation | batch_69de8c0ef8a4819092d84478b1f56db1 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:45 a.m.