Triple
T3747774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Italian tricolour naval ensign |
E81248
|
entity |
| Predicate | fieldRatio |
P1991
|
FINISHED |
| Object | 2:3 |
—
|
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: 2:3 | Statement: [Italian tricolour naval ensign, fieldRatio, 2:3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldRatio Context triple: [Italian tricolour naval ensign, fieldRatio, 2:3]
-
A.
aspectRatio
chosen
Indicates the proportional relationship between an entity’s width and its height.
-
B.
hasFocalRatio
Indicates a relationship where an optical system is associated with a specific focal ratio (f-number) that characterizes its light-gathering speed and image brightness.
-
C.
pegRatio
Indicates the relationship between a company’s price-to-earnings (P/E) ratio and its expected earnings growth rate, expressing how highly the market values each unit of anticipated growth.
-
D.
areaScale
Indicates a proportional relationship where one area value is a scaled (enlarged or reduced) version of another by a specific factor.
-
E.
hasFocalRatioRange
Indicates that an entity is associated with a range of possible focal ratios, specifying the minimum and maximum f-number values it can have.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.