Triple
T33600531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontong Java language |
E860703
|
entity |
| Predicate | hasSuperstrateContact |
P199840
|
FINISHED |
| Object | English |
—
|
NE NERFINISHED |
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: English | Statement: [Ontong Java language, hasSuperstrateContact, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSuperstrateContact Context triple: [Ontong Java language, hasSuperstrateContact, English]
-
A.
hasSuperstrate
Indicates that one material, layer, or structure lies above and is supported by another in a layered or composite arrangement.
-
B.
hasBottomSubstrate
Indicates that one entity serves as the underlying or supporting substrate or base layer for another entity.
-
C.
isInContactWith
Indicates that two entities are physically touching or directly connected so that contact between them is established.
-
D.
hasSubsurfaceStructure
Indicates that an entity possesses or contains a structural component located beneath its visible or external surface.
-
E.
hasSurfaceConnection
Indicates that two entities are directly connected or in contact at their surfaces, allowing interaction or continuity between them.
- F. None of above. chosen
Provenance (4 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff5b233e9c8190adc06cca0758986b |
completed | May 9, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ff5a5682108190a006b23c4fcdcc7c |
completed | May 9, 2026, 4:01 p.m. |
| PDg | Predicate description generation | batch_69ff5b224b8c8190bd0955876098ecc8 |
completed | May 9, 2026, 4:04 p.m. |
Created at: May 1, 2026, 1:41 a.m.