Triple
T7235210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hanunoo language |
E155204
|
entity |
| Predicate | hasScriptTool |
P75935
|
FINISHED |
| Object | knife |
—
|
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: knife | Statement: [Hanunoo language, hasScriptTool, knife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptTool Context triple: [Hanunoo language, hasScriptTool, knife]
-
A.
hasScriptUsage
Indicates that one entity uses, employs, or is written in the script or writing system specified by another entity.
-
B.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
E.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6ea539f5c81908001524149903559 |
completed | March 27, 2026, 8:36 p.m. |
Created at: March 27, 2026, 2:55 p.m.