Triple
T34661305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridin' Shotgun |
E890115
|
entity |
| Predicate | mainPerformerMovement |
P183542
|
FINISHED |
| Object | outlaw country movement |
—
|
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: outlaw country movement | Statement: [Ridin' Shotgun, mainPerformerMovement, outlaw country movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerMovement Context triple: [Ridin' Shotgun, mainPerformerMovement, outlaw country movement]
-
A.
movementFunction
Indicates a functional or operational role related to enabling, controlling, or characterizing movement between entities.
-
B.
motionCapturePerformer
Indicates a relationship where a performer provides motion data, typically through sensors or tracking, to drive the movement of a digital character or animation.
-
C.
movementPeriod
Indicates the span of time during which a movement or motion occurs or is valid.
-
D.
movementSystem
Indicates a relationship where an entity is part of, uses, or is governed by a particular system that enables or controls its movement.
-
E.
movementProduction
Indicates a relationship where an entity generates, initiates, or causes physical movement or motion.
- F. None of above. chosen
Provenance (4 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7a01efcc08190bba489a9099b8684 |
completed | May 3, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79f477c4c8190a35cb6d87b1dcbd1 |
completed | May 3, 2026, 7:17 p.m. |
Created at: May 1, 2026, 2:04 a.m.