Triple
T18991910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinson cup anemometer |
E464702
|
entity |
| Predicate | canBeConnectedTo |
P107489
|
FINISHED |
| Object | data logger |
—
|
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: data logger | Statement: [Robinson cup anemometer, canBeConnectedTo, data logger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeConnectedTo Context triple: [Robinson cup anemometer, canBeConnectedTo, data logger]
-
A.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
B.
canBeLinkedTo
chosen
Indicates that one entity has the potential or capability to be connected or associated with another entity.
-
C.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
D.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
E.
connectsViaCanal
Indicates that one entity is linked or joined to another by means of a canal.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67dee4c8190ac2017ff748ea6aa |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.