Triple
T13358561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F-5 |
E318759
|
entity |
| Predicate | setupPosition |
P81693
|
FINISHED |
| Object | fireman’s carry |
—
|
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: fireman’s carry | Statement: [F-5, setupPosition, fireman’s carry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setupPosition Context triple: [F-5, setupPosition, fireman’s carry]
-
A.
createsPosition
Indicates that one entity establishes or originates a new role, job, or position for another entity or within an organization.
-
B.
defaultPosition
chosen
Indicates the standard or initial spatial arrangement or pose that an entity assumes in the absence of other specified positions.
-
C.
initiallyPositionedAs
Indicates that one entity’s starting or original position is specified relative to another entity or reference frame.
-
D.
initiatingPosition
Indicates the starting location or initial spatial position from which an action, process, or movement begins.
-
E.
establishedByPosition
Indicates that a relationship or status is created or determined based on an entity’s role, rank, or positional placement within a structure or system.
- 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_69d806b7bbac8190b85278c87fa7aff3 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69da62887e588190bd7241c720a112a2 |
completed | April 11, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69d9a02c9abc8190b328e7bae747bfc5 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:32 p.m.