Triple
T36705410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lipayran |
E906344
|
entity |
| Predicate | hasCommonTransport |
P199897
|
FINISHED |
| Object | outrigger boats |
—
|
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: outrigger boats | Statement: [Lipayran, hasCommonTransport, outrigger boats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommonTransport Context triple: [Lipayran, hasCommonTransport, outrigger boats]
-
A.
hasTransportMethod
chosen
Indicates that one entity uses, provides, or is associated with a particular means or mode of transportation to move people or goods.
-
B.
hasTransporters
Indicates that one entity possesses, provides, or is equipped with one or more means of transportation for another entity or purpose.
-
C.
hasTransportServices
Indicates that one entity provides or operates transport services for, or in connection with, another entity or location.
-
D.
hasTransportAcross
Indicates that one entity provides or enables transportation across another entity, such as a barrier, region, or medium.
-
E.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.