Triple
T29065554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brock (M20 barrier system nickname) |
E735663
|
entity |
| Predicate | semanticReference |
P53956
|
FINISHED |
| Object | badger |
—
|
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: badger | Statement: [Brock (M20 barrier system nickname), semanticReference, badger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: semanticReference Context triple: [Brock (M20 barrier system nickname), semanticReference, badger]
-
A.
symbolReferenced
chosen
Indicates that one symbol is mentioned, cited, or otherwise referred to by another symbol.
-
B.
referenceSectionFor
Indicates a relationship where one resource serves as the reference section or reference material specifically associated with another resource.
-
C.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
D.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
E.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
- 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6609a8bfc8190bbf7855ef75416c2 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 10:17 a.m.