Triple
T20437800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Apostles |
E501300
|
entity |
| Predicate | figureScale |
P57293
|
FINISHED |
| Object | life-size |
—
|
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: life-size | Statement: [Four Apostles, figureScale, life-size]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: figureScale Context triple: [Four Apostles, figureScale, life-size]
-
A.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
B.
coversScale
Indicates that one entity spans, includes, or applies across the full range or extent of another entity’s scale.
-
C.
userScale
Indicates that a user adjusts or sets the scale, size, or zoom level of an object, interface, or content.
-
D.
similarScaleTo
chosen
Indicates that two entities have comparable magnitude, size, or extent along a given dimension or measurement scale.
-
E.
associatedScale
Indicates that one entity is linked or connected to a particular scale used to measure, classify, or evaluate it.
- 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_69e0b4ab3cfc8190ac9bf32e932316b1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e685f042988190948253a3d2ee4e9e |
completed | April 20, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:31 a.m.