Triple
T20391679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tricorder |
E498099
|
entity |
| Predicate | canInterfaceWith |
P110757
|
FINISHED |
| Object | starship computer |
—
|
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: starship computer | Statement: [tricorder, canInterfaceWith, starship computer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canInterfaceWith Context triple: [tricorder, canInterfaceWith, starship computer]
-
A.
usesInterface
Indicates that one entity interacts with or operates another entity through a specified interface or set of interface methods.
-
B.
designedToInterfaceWith
chosen
Indicates that one entity has been intentionally created or configured to connect, interact, or work compatibly with another entity.
-
C.
hasInterface
Indicates that one entity provides, exposes, or is connected through a defined interface to another entity.
-
D.
hasCommunicationInterface
Indicates that one entity provides or supports a specific means or channel through which it can communicate or exchange data with another entity or system.
-
E.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
- 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_69e0b4a71ebc8190b153a36c738730f4 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e679108b1481909677cf80e8e77e76 |
completed | April 20, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:28 a.m.