Triple
T2157714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gutenberg Bible copies |
E47929
|
entity |
| Predicate | haveScript |
P5713
|
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: [Gutenberg Bible copies, haveScript, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveScript Context triple: [Gutenberg Bible copies, haveScript, Latin script]
-
A.
containsScript
chosen
Indicates that one entity includes or embeds the script of another entity within it.
-
B.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
C.
scriptOnFlag
Indicates that a script is attached to and/or executed when a specific flag or condition is set.
-
D.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
E.
usesScriptDerivedFrom
Indicates that one entity employs a writing system that is historically or structurally derived from the script used by 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe68fe0c8190beb5db003738a6e5 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9a60648190b20b116be5c7ad98 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.