Triple
T367544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | An Inquiry into the Nature and Progress of Rent |
E7994
|
entity |
| Predicate | hasAuthorialOccupation |
P938
|
FINISHED |
| Object | political economist |
—
|
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: political economist | Statement: [An Inquiry into the Nature and Progress of Rent, hasAuthorialOccupation, political economist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorialOccupation Context triple: [An Inquiry into the Nature and Progress of Rent, hasAuthorialOccupation, political economist]
-
A.
authorOccupation
chosen
Indicates the professional role or job that an author holds or is associated with.
-
B.
hasAuthor
Indicates that an entity is written or created by a specific author.
-
C.
authorshipStatus
Indicates the current state or condition of an entity’s role as an author in relation to a work (e.g., confirmed, disputed, anonymous, or pending).
-
D.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
E.
hasCoauthor
Indicates that two or more entities have jointly authored the same work or publication.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebe92c7c8190b49af2b2b461eacc |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95ede588190998fdf3a6ea90498 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.