Triple
T18016033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COCO |
E431000
|
entity |
| Predicate | hasAnnotationType |
P4981
|
FINISHED |
| Object | object bounding boxes |
—
|
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: object bounding boxes | Statement: [COCO, hasAnnotationType, object bounding boxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnnotationType Context triple: [COCO, hasAnnotationType, object bounding boxes]
-
A.
typeOfAnnotation
chosen
Indicates that one entity is an annotation and specifies the kind or category of that annotation in relation to the annotated item.
-
B.
hasAncestralType
Indicates that one type is derived from, or originates from, another more primitive or original type in an inheritance or lineage hierarchy.
-
C.
hasAssociatedType
Indicates that one entity is linked to another entity that specifies its type, category, or classification.
-
D.
hasBeanType
Indicates that an entity is associated with or characterized by a specific type or category of bean.
-
E.
hasMethodType
Indicates that an entity is associated with, or characterized by, a specific type or category of method used or applied in its context.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b523f588819097389e067dda7f23 |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.