Triple
T21396640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iranun people |
E527802
|
entity |
| Predicate | traditionalVesselType |
P114166
|
FINISHED |
| Object | lanong warship |
—
|
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: lanong warship | Statement: [Iranun people, traditionalVesselType, lanong warship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalVesselType Context triple: [Iranun people, traditionalVesselType, lanong warship]
-
A.
traditionalVessel
Indicates that one entity is a vessel or container that follows traditional, customary, or historically established forms, designs, or uses in relation to another entity.
-
B.
hasTraditionalBoatType
chosen
Indicates that an entity is associated with or characterized by a specific traditional type of boat.
-
C.
usesVesselType
Indicates that an entity performs an activity or operation by employing a specific type or category of vessel.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
- 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_69e0b51ff3748190935c0a513c62a12b |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e8b11a2aec8190a60e53b90d0823b1 |
completed | April 22, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:13 p.m.