Triple
T5088849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 5/No. 22 |
E114703
|
entity |
| Predicate | hasRectangularFormat |
P17102
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [No. 5/No. 22, hasRectangularFormat, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRectangularFormat Context triple: [No. 5/No. 22, hasRectangularFormat, yes]
-
A.
isRectangular
Indicates that an object or shape has the properties of a rectangle, typically with four sides and right angles between adjacent sides.
-
B.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
hasPanelFormat
chosen
Indicates that something is associated with a particular panel layout or format used for its presentation or display.
-
D.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
E.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd753f6544819090c028b34ee87536 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd715c0a448190afc837c6c31dc6ab |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.