Triple
T29111682
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pagsanjan |
E736924
|
entity |
| Predicate | transportModeToFalls |
P117172
|
FINISHED |
| Object | wooden canoes |
—
|
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: wooden canoes | Statement: [Pagsanjan, transportModeToFalls, wooden canoes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeToFalls Context triple: [Pagsanjan, transportModeToFalls, wooden canoes]
-
A.
transportModeTo
chosen
Indicates the means or mode of transportation used to travel to a specified destination.
-
B.
transportPattern
Indicates a recurring or characteristic way in which transportation is carried out between entities, such as typical routes, modes, or schedules.
-
C.
transportModeFamily
Indicates the general category or family of transportation mode to which a specific transport mode belongs (e.g., road, rail, air, water).
-
D.
roadTransportFunction
Indicates a functional relationship in which something serves or is used for the transport of people or goods via roads.
-
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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: April 28, 2026, 11:19 a.m.