Triple
T2545260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swiss Guard |
E57882
|
entity |
| Predicate | minimumHeightRequirement |
P8078
|
FINISHED |
| Object | 174 cm |
—
|
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: 174 cm | Statement: [Swiss Guard, minimumHeightRequirement, 174 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minimumHeightRequirement Context triple: [Swiss Guard, minimumHeightRequirement, 174 cm]
-
A.
heightRestriction
chosen
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
maximumAgeRequirement
Indicates that there is an upper age limit that an entity must not exceed in order for a condition, participation, or eligibility to apply.
-
C.
minimumWidth
Indicates that there is a specified smallest allowable or required width for something in the relationship.
-
D.
establishedMandatoryMinimum
Indicates that an authority has set a required minimum level, amount, or standard that must be met or exceeded.
-
E.
requiresMinimumScore
Indicates that one entity can only be obtained, accessed, or considered valid if another entity’s score meets or exceeds a specified minimum threshold.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.