Triple
T13475483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MALAYSIAN THREE SEVEN ZERO |
E318238
|
entity |
| Predicate | spokenDigits |
P104512
|
FINISHED |
| Object | three seven zero |
—
|
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: three seven zero | Statement: [MALAYSIAN THREE SEVEN ZERO, spokenDigits, three seven zero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spokenDigits Context triple: [MALAYSIAN THREE SEVEN ZERO, spokenDigits, three seven zero]
-
A.
spellsOut
Indicates that one entity explicitly writes, states, or presents another entity in full detail, often by expanding an abbreviation, code, or symbolic form into its complete representation.
-
B.
digitSymbolForOne
Indicates that something is the written or symbolic representation used to denote the numeric value one.
-
C.
digitForThree
Indicates that something serves as the numeral or symbol used to represent the number three.
-
D.
digitForSeven
Indicates that something serves as the digit representation specifically for the number seven.
-
E.
numberDescribedAs
chosen
Indicates that a number is characterized, labeled, or referred to using a particular description or phrase.
- 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf2551b48190a074fd256791742d |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:42 p.m.