Triple
T5690849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hunminjeongeum |
E125423
|
entity |
| Predicate | scriptDescribed |
P51137
|
FINISHED |
| Object | featural alphabet |
—
|
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: featural alphabet | Statement: [Hunminjeongeum, scriptDescribed, featural alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptDescribed Context triple: [Hunminjeongeum, scriptDescribed, featural alphabet]
-
A.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
B.
scriptFeature
chosen
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
C.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
D.
describedIn
Indicates that information about an entity is contained or documented within a specified source, such as a text, document, or media.
-
E.
scriptEvolution
Indicates how a script or written system changes, develops, or transforms over time in relation to its earlier or later forms.
- 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_69c0082bb19c8190823a4facd3cba79b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.