Triple
T35806450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People’s Elbow |
E1035111
|
entity |
| Predicate | isWork |
P184132
|
FINISHED |
| Object | scripted maneuver |
—
|
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: scripted maneuver | Statement: [People’s Elbow, isWork, scripted maneuver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWork Context triple: [People’s Elbow, isWork, scripted maneuver]
-
A.
ownsWork
Indicates that one entity has legal ownership or proprietary rights over a particular work or creation.
-
B.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
C.
worksDuring
Indicates that an entity performs work or is on duty throughout a specified time period or schedule.
-
D.
usedForWork
Indicates that something is employed or utilized to perform tasks, duties, or activities related to a job or occupation.
-
E.
worksOver
Indicates that one entity performs work that extends beyond or exceeds a certain limit, threshold, or standard associated with another entity.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:06 p.m.