Triple
T19421558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frisian handball |
E485866
|
entity |
| Predicate | fieldMarking |
P51959
|
FINISHED |
| Object | service box |
—
|
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: service box | Statement: [Frisian handball, fieldMarking, service box]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldMarking Context triple: [Frisian handball, fieldMarking, service box]
-
A.
routeMarkingStandard
Indicates the standard or convention used to mark or signpost a particular route.
-
B.
colorOfTrailMarkings
Indicates the relationship specifying what color the trail’s markings are.
-
C.
hasFloorMarkings
chosen
Indicates that an entity features visible markings or lines on its floor surface, typically used for guidance, organization, or safety.
-
D.
markingFeature
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
E.
coatMarkings
Indicates how an entity’s coat is patterned or marked, such as stripes, spots, or other distinctive visual markings.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63214d768819082129100d7116521 |
completed | April 20, 2026, 2:03 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.