Triple
T23529995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine linguistic area |
E576536
|
entity |
| Predicate | hasDefiningProcess |
P1410
|
FINISHED |
| Object | language contact |
—
|
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: language contact | Statement: [Philippine linguistic area, hasDefiningProcess, language contact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDefiningProcess Context triple: [Philippine linguistic area, hasDefiningProcess, language contact]
-
A.
hasProcess
chosen
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
B.
hasDefinition
Indicates that one entity provides the meaning, explanation, or definition of another entity.
-
C.
hasSubProcess
Indicates that one process is composed of or includes another process as a subordinate or component step.
-
D.
hasDefinitionSource
Indicates that the definition of an entity originates from or is documented in a specified source.
-
E.
definesProcessFor
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
- 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_69e245f5a8848190a2ba42e271c6c31f |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1ac7646a48190b5dcbaf8c0c194df |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:09 p.m.