Triple
T4249837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperCam |
E95820
|
entity |
| Predicate | canAnalyzeFromDistance |
P37106
|
FINISHED |
| Object | up to several 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: up to several meters | Statement: [SuperCam, canAnalyzeFromDistance, up to several meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canAnalyzeFromDistance Context triple: [SuperCam, canAnalyzeFromDistance, up to several meters]
-
A.
hasApproximateDistanceScale
Indicates that one entity is related to another by a distance measure that is approximate or estimated rather than exact.
-
B.
approximateDistanceFrom
chosen
Indicates an estimated or rough measure of how far one entity is from another.
-
C.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
D.
canDetermine
Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
-
E.
tieneAlcance
Indicates that something possesses or has a certain scope, reach, or range of effect in relation to something else.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9f11008190a0021e0ad730a79d |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:06 p.m.