Triple
T5592380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garnett-Allen-Pierce trio |
E146909
|
entity |
| Predicate | positionCombination |
P29748
|
FINISHED |
| Object | forward-guard-forward |
—
|
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: forward-guard-forward | Statement: [Garnett-Allen-Pierce trio, positionCombination, forward-guard-forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionCombination Context triple: [Garnett-Allen-Pierce trio, positionCombination, forward-guard-forward]
-
A.
positionInCase
Indicates the specific role, status, or placement that an entity holds within a particular case or legal proceeding.
-
B.
positionB
Indicates that one entity occupies or is located at a specific position relative to another entity.
-
C.
positionGroup
chosen
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
D.
positionA
Indicates the spatial or ordered position of an entity A within a defined reference frame or sequence.
-
E.
positionUse
Indicates how a particular position or role is utilized or functionally applied within a given 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_69c009036c408190981a8d690b679b67 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020bb08648190ab1f66cc3e897e6d |
completed | March 22, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69c01b16b9bc8190ab0b945507d90e05 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:38 p.m.