Triple
T18204857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XLM-R |
E435876
|
entity |
| Predicate | handlesScriptTypes |
P109281
|
FINISHED |
| Object | Latin |
—
|
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 | Statement: [XLM-R, handlesScriptTypes, Latin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: handlesScriptTypes Context triple: [XLM-R, handlesScriptTypes, Latin]
-
A.
scriptType
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
B.
appliesToScript
chosen
Indicates that something (such as a rule, configuration, or operation) is specifically relevant or applicable to a given script.
-
C.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
D.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
-
E.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e222831081908f7d5500424e3acb |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.