Triple
T720262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balinese script |
E14599
|
entity |
| Predicate | hasIndependentDigitZero |
P18522
|
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: [Balinese script, hasIndependentDigitZero, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndependentDigitZero Context triple: [Balinese script, hasIndependentDigitZero, true]
-
A.
isZeroFor
Indicates that a given value, expression, or function evaluates to zero when applied to or considered with respect to a specified entity or context.
-
B.
hasDigitCount
Indicates that one entity has a total number of digits equal to the value specified by the other entity.
-
C.
isNonzeroFor
Indicates that a given value, function, or quantity is not equal to zero under specified conditions or for specified inputs.
-
D.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
E.
hasParity
Indicates that two entities share the same parity property (e.g., both even or both odd) with respect to a specified attribute or value.
- 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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58e65e8819098cba7e6a20d8f33 |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.