Triple
T11961552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal of Political Economy |
E284679
|
entity |
| Predicate | hasDOIRegistration |
P8687
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Journal of Political Economy, hasDOIRegistration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDOIRegistration Context triple: [Journal of Political Economy, hasDOIRegistration, true]
-
A.
hasDigitalObjectIdentifier
chosen
Indicates that an entity is associated with a specific Digital Object Identifier (DOI) that uniquely identifies it in a digital environment.
-
B.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
C.
hasCitationSystem
Indicates that one entity uses, follows, or is governed by a particular citation or referencing system defined by another entity.
-
D.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
-
E.
hasORCID
Indicates that an entity is associated with a specific ORCID identifier, representing a unique researcher or contributor ID.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9037848f481908276716675464464 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.