Triple
T11206685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryūō |
E265182
|
entity |
| Predicate | hasNameScript |
P63723
|
FINISHED |
| Object | Latin alphabet transcription |
—
|
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 alphabet transcription | Statement: [Ryūō, hasNameScript, Latin alphabet transcription]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameScript Context triple: [Ryūō, hasNameScript, Latin alphabet transcription]
-
A.
hasScriptName
Indicates that an entity is associated with a specific script or writing system identified by a particular name.
-
B.
hasNameInTeluguScript
Indicates that an entity is associated with a name written in the Telugu script.
-
C.
hasNameFunction
Indicates that an entity is associated with a function whose purpose is to provide or determine its name.
-
D.
containsScript
Indicates that one entity includes or embeds the script of another entity within it.
-
E.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
- 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_69d6aac59460819089b9848b27f57848 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.