Triple
T30645310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lay magistrates |
E780103
|
entity |
| Predicate | isPaidPosition |
P169655
|
FINISHED |
| Object | unpaid |
—
|
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: unpaid | Statement: [Lay magistrates, isPaidPosition, unpaid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPaidPosition Context triple: [Lay magistrates, isPaidPosition, unpaid]
-
A.
isPayoffFor
Indicates that one entity serves as the reward, benefit, or outcome received in return for another entity’s action, investment, or event.
-
B.
isPositionedAs
Indicates that one entity is placed or arranged in a specific spatial or conceptual position relative to another.
-
C.
positionEligible
Indicates that an entity is qualified or permitted to hold or be assigned to a particular position or role.
-
D.
offeredPosition
Indicates that one entity has extended a job or role opportunity to another entity.
-
E.
hasPaidStaff
Indicates that an entity employs and compensates one or more individuals as staff.
- 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_69f224a50ebc81909b961a94c7f66b12 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9342b08190adbc5ede24cadd7f |
completed | May 2, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f67f0353c88190a05b2db449abe0f4 |
completed | May 2, 2026, 10:47 p.m. |
Created at: April 29, 2026, 8:29 p.m.