Triple
T8551888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zorro III |
E202462
|
entity |
| Predicate | busConnectorLocation |
P83575
|
FINISHED |
| Object | Amiga motherboard |
—
|
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: Amiga motherboard | Statement: [Zorro III, busConnectorLocation, Amiga motherboard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busConnectorLocation Context triple: [Zorro III, busConnectorLocation, Amiga motherboard]
-
A.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
-
B.
transportationJunctionFor
Indicates a location that serves as a connecting point where multiple transportation routes or modes meet, intersect, or transfer.
-
C.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
D.
accessByBusFrom
Indicates that one location can be reached from another location using a bus as the mode of transportation.
-
E.
hasBusStation
Indicates that a place or area contains or is served by a bus station.
- 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_69ca832610e08190b3b6c6cd2c250255 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe886fb788190a73e7c76c4f86409 |
completed | March 31, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69cbd113e05c81908f4f3fc1b5925164 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:19 p.m.