Triple
T3047981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyoda Automatic Loom Works |
E83494
|
entity |
| Predicate | technologyLegacy |
P45324
|
FINISHED |
| Object | automatic loom patents |
—
|
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: automatic loom patents | Statement: [Toyoda Automatic Loom Works, technologyLegacy, automatic loom patents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyLegacy Context triple: [Toyoda Automatic Loom Works, technologyLegacy, automatic loom patents]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
technologyGeneration
Indicates the generational level or era of technology associated with or used by an entity in relation to another.
-
C.
technologyLineage
Indicates a relationship where one technology is derived from, influenced by, or evolved from another in a historical or developmental sequence.
-
D.
technologyPioneered
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
E.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
- 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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9baed3848190a8351d9c8c4edc79 |
completed | March 8, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
| PDg | Predicate description generation | batch_69ad9b272a408190ba0ce09bdeea76c9 |
completed | March 8, 2026, 3:52 p.m. |
Created at: March 8, 2026, 3:01 p.m.