Triple
T1188379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian jiu-jitsu |
E25299
|
entity |
| Predicate | typicalPositions |
P12230
|
FINISHED |
| Object | guard |
—
|
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: guard | Statement: [Brazilian jiu-jitsu, typicalPositions, guard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPositions Context triple: [Brazilian jiu-jitsu, typicalPositions, guard]
-
A.
typicalPositionBias
Indicates a systematic tendency for something to be placed, chosen, or interpreted in a commonly favored or default position relative to other options.
-
B.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalTimes
Indicates the usual or characteristic times at which an event, activity, or condition typically occurs.
-
D.
typicalPilotPosition
Indicates the usual or standard spatial position or placement where a pilot is located relative to the associated object or system.
-
E.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd568cf481908d10cf19a3ce28f3 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:45 p.m.