Triple
T22653184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manuale Tipografico |
E559146
|
entity |
| Predicate | scriptSystemsIncluded |
P149077
|
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: [Manuale Tipografico, scriptSystemsIncluded, Latin script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptSystemsIncluded Context triple: [Manuale Tipografico, scriptSystemsIncluded, Latin script]
-
A.
modelsSystemsWith
Indicates that one entity creates or uses a representation or abstraction to describe, analyze, or simulate another system.
-
B.
seriesIncludes
Indicates that a particular series contains or encompasses the referenced item as one of its constituent parts.
-
C.
softwareIncluded
Indicates that certain software is bundled with, provided alongside, or contained within another item or offering.
-
D.
scriptSystem
Indicates that one entity is the scripting or programming system used to control, configure, or automate the behavior of another entity.
-
E.
isPartOfSystemWithFeature
Indicates that one entity belongs to a system that possesses a specified feature or characteristic.
- F. None of above. chosen
Provenance (4 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17659e4dc81909cf6943c1c986ef9 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:06 p.m.