Triple
T2188022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC |
E49795
|
entity |
| Predicate | communicationRange |
P14301
|
FINISHED |
| Object | up to 10 cm |
—
|
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 10 cm | Statement: [NFC, communicationRange, up to 10 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationRange Context triple: [NFC, communicationRange, up to 10 cm]
-
A.
maximumReach
chosen
Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
-
B.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
C.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
D.
enablesCommunicationWith
Indicates that one entity provides the means or capability for another entity to communicate with a specified party or system.
-
E.
hostRange
Indicates the range or set of different hosts that an organism, agent, or system can successfully inhabit, infect, or interact with.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.