Triple
T21743587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Brother |
E536725
|
entity |
| Predicate | primaryModeOfTravelOnEarth |
P113005
|
FINISHED |
| Object | on foot |
—
|
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: on foot | Statement: [The Brother, primaryModeOfTravelOnEarth, on foot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryModeOfTravelOnEarth Context triple: [The Brother, primaryModeOfTravelOnEarth, on foot]
-
A.
primaryTransports
Indicates that one entity serves as the main means or method of transporting or conveying another entity.
-
B.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
C.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
-
D.
usedTransportationMode
chosen
Indicates that an entity traveled or moved using a specified mode of transportation.
-
E.
transportModeFamily
Indicates the general category or family of transportation mode to which a specific transport mode belongs (e.g., road, rail, air, water).
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a74592c8190959af631d72df479 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.