Triple
T19047714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book from the Sky |
E466177
|
entity |
| Predicate | scriptAppearance |
P10534
|
FINISHED |
| Object | resembles traditional Chinese 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: resembles traditional Chinese script | Statement: [Book from the Sky, scriptAppearance, resembles traditional Chinese script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAppearance Context triple: [Book from the Sky, scriptAppearance, resembles traditional Chinese script]
-
A.
scriptFeature
Indicates that a script includes, supports, or is characterized by a particular feature or capability.
-
B.
publicAppearance
Indicates that an entity participates in or is present at an event or situation that is open or visible to the general public.
-
C.
compilationAppearance
Indicates that an entity appears as part of a compilation, such as being included within a collected or aggregated work.
-
D.
scriptOnBlade
Indicates that there is writing or inscription present on the blade of an object.
-
E.
scriptStyle
chosen
Indicates that one entity specifies or characterizes the stylistic form or manner of a script associated with another entity.
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d8057dec8190b9f1e0b54084ecec |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.