Triple
T9714304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orya |
E235100
|
entity |
| Predicate | scriptCodeLength |
P90394
|
FINISHED |
| Object | 4 letters |
—
|
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: 4 letters | Statement: [Orya, scriptCodeLength, 4 letters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptCodeLength Context triple: [Orya, scriptCodeLength, 4 letters]
-
A.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
B.
instructionLength
Indicates the duration or amount of time required to carry out a given instruction or operation.
-
C.
linesOfCodeApprox
Indicates an approximate or estimated number of lines of code associated with an entity.
-
D.
scriptCodeContext
Indicates that a script is written or executed within a particular code context or environment.
-
E.
statisticsCode
Indicates that an entity is associated with a specific statistics-related code used for classification, reporting, or analysis.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e0a1b548190b34c8571751ca1d3 |
completed | April 1, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
| PDg | Predicate description generation | batch_69cd06aa8bc88190904be19c8953def8 |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:19 p.m.