Triple
T12756377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City and South London Railway |
E304869
|
entity |
| Predicate | initialCarDesign |
P1529
|
FINISHED |
| Object | no side windows |
—
|
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: no side windows | Statement: [City and South London Railway, initialCarDesign, no side windows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialCarDesign Context triple: [City and South London Railway, initialCarDesign, no side windows]
-
A.
firstCarCoachbuilder
Indicates that the object is the coachbuilder responsible for constructing the body of the subject’s first car.
-
B.
vehicleDeveloped
Indicates that an entity (such as a person, organization, or group) created, designed, or otherwise developed a particular vehicle.
-
C.
hasDesignOrigin
Indicates that one entity is the source, inspiration, or original model from which the design of another entity is derived.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
- 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_69d7bdf1fcd081909ffb0e0d6fa3a07d |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d8b57b88190b29b8fdca415c81c |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:27 p.m.