Triple
T32427308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ES-125 |
E828610
|
entity |
| Predicate | stringAnchoring |
P149257
|
FINISHED |
| Object | trapeze tailpiece anchoring |
—
|
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: trapeze tailpiece anchoring | Statement: [ES-125, stringAnchoring, trapeze tailpiece anchoring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stringAnchoring Context triple: [ES-125, stringAnchoring, trapeze tailpiece anchoring]
-
A.
anchoredBy
Indicates that one entity is fixed, secured, or held in place by another acting as its anchor.
-
B.
coAnchorWith
Indicates that two or more people jointly serve as anchors or hosts of the same program, segment, or broadcast.
-
C.
anchorPoint
chosen
Indicates a fixed reference position used to attach, align, or position one entity relative to another.
-
D.
alignmentRange
Indicates a relationship where one entity’s alignment or position is constrained to fall within a specified range defined by another entity or set of parameters.
-
E.
segmentPositioning
Indicates how segments are arranged or ordered relative to one another within a larger structure or sequence.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2a85d4c81909c399aaecc7c440b |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.