Triple
T27458695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BR-10 |
E692671
|
entity |
| Predicate | scriptOfCodePrefix |
P168084
|
FINISHED |
| Object | Latin script |
—
|
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: Latin script | Statement: [BR-10, scriptOfCodePrefix, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfCodePrefix Context triple: [BR-10, scriptOfCodePrefix, Latin script]
-
A.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
B.
languageOfCodePrefix
Indicates that one entity is the programming language associated with, or identified by, the code prefix represented by the other entity.
-
C.
topLevelCodePrefix
Indicates that one code serves as a primary or highest-level prefix from which another, more specific code is derived or categorized.
-
D.
tailCodePrefix
Indicates that one entity’s tail code begins with, or is prefixed by, the string represented by the other entity.
-
E.
scriptCodeContext
Indicates that a script is written or executed within a particular code context or environment.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f673633d288190b52ceb9f8a057c44 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ec3d3d48190ab2f2b71939e572e |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 27, 2026, 12:49 p.m.