Triple
T13769474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maslog |
E330839
|
entity |
| Predicate | hasRiverineCommunities |
P56551
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Maslog, hasRiverineCommunities, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverineCommunities Context triple: [Maslog, hasRiverineCommunities, true]
-
A.
hasVillageOnRiver
Indicates that a village is located on or alongside a particular river.
-
B.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
C.
riverineSettlement
Indicates that a settlement is located on or closely associated with the banks or course of a river.
-
D.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
-
E.
riverinePeople
chosen
Indicates a relationship where people live along, depend on, or are closely associated with rivers and river environments.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0233ecc48190b934f085d2501eb1 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:10 p.m.