Triple
T36978296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Metropolitan |
E914754
|
entity |
| Predicate | capPosting |
P186841
|
FINISHED |
| Object | designed to post securely on barrel |
—
|
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: designed to post securely on barrel | Statement: [Pilot Metropolitan, capPosting, designed to post securely on barrel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capPosting Context triple: [Pilot Metropolitan, capPosting, designed to post securely on barrel]
-
A.
caps
Indicates that one entity serves as the capital city or administrative center of another entity, such as a country, state, or region.
-
B.
capTreatment
Indicates a medical or corrective treatment applied to a tooth’s crown (cap), such as placing or modifying a dental cap or crown.
-
C.
caption
Indicates that a piece of text serves as a descriptive label or explanation for an associated image, video, or other media content.
-
D.
postPosition
Indicates that one entity is located behind or to the rear of another entity in space or sequence.
-
E.
captures
Indicates that one entity seizes, traps, or takes control of another entity, often preventing its escape or freedom.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.