Triple
T3567985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Mews |
E75496
|
entity |
| Predicate | transportTypeManaged |
P1379
|
FINISHED |
| Object | horse-drawn carriages |
—
|
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: horse-drawn carriages | Statement: [Royal Mews, transportTypeManaged, horse-drawn carriages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportTypeManaged Context triple: [Royal Mews, transportTypeManaged, horse-drawn carriages]
-
A.
transportType
chosen
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
C.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
D.
transportAgnostic
Indicates that the relationship or action is independent of, and unaffected by, the specific transport mechanism or communication channel used.
-
E.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
- 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_69ad85d512708190829c8b2d3a2ccfb8 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc0ab51d881908f004fae47ab09d9 |
completed | March 8, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69adb8364d848190a96a9bc7a6126af2 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:21 p.m.