Triple
T4124872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Tower |
E92699
|
entity |
| Predicate | technologyConcept |
P54422
|
FINISHED |
| Object | resonant inductive coupling |
—
|
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: resonant inductive coupling | Statement: [Tesla Tower, technologyConcept, resonant inductive coupling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyConcept Context triple: [Tesla Tower, technologyConcept, resonant inductive coupling]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyParadigm
Indicates a relationship where one entity represents or defines the overarching technological model, framework, or approach within which another entity operates or is categorized.
-
C.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
-
D.
technologyPresent
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
E.
technologyField
Indicates the area or domain of technology in which an entity is involved, specialized, or categorized.
- 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_69aed9685f70819086932777aec8d959 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.