Triple
T19111529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beaufort scale |
E467801
|
entity |
| Predicate | hasHighestForceNumber |
P134454
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Beaufort scale, hasHighestForceNumber, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestForceNumber Context triple: [Beaufort scale, hasHighestForceNumber, 12]
-
A.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
B.
isHighestRangeOf
Indicates that one entity represents the maximum or topmost range or interval within which another entity falls or is categorized.
-
C.
isHighestOfGroup
Indicates that an entity has the greatest value or rank within a specified group, with no other member exceeding it.
-
D.
hasHighestStructure
Indicates that an entity possesses the tallest or most elevated structural feature compared to all other relevant entities in a given context.
-
E.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e394969c81909d09b2300ea0e041 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9ac41848190afd0f33b42cebe99 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.