Triple
T35097477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minimundus |
E1012904
|
entity |
| Predicate | hasScaleRange |
P144633
|
FINISHED |
| Object | 1:25 |
—
|
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: 1:25 | Statement: [Minimundus, hasScaleRange, 1:25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScaleRange Context triple: [Minimundus, hasScaleRange, 1:25]
-
A.
hasScale
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
B.
hasScaleSize
chosen
Indicates that one entity possesses a scale characterized by a particular size or magnitude in relation to another entity or value.
-
C.
hasScaleSeries
Indicates that one entity is associated with a particular ordered set or sequence of scales used for measurement, evaluation, or representation.
-
D.
hasScales
Indicates that an entity possesses scales as a surface covering or body feature.
-
E.
hasScaleParameter
Indicates that an entity is associated with a scale parameter that controls the magnitude or dispersion of a related quantity or distribution.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:01 p.m.