Triple
T4172566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arctic Home in the Vedas |
E86396
|
entity |
| Predicate | publisherStatus |
P54520
|
FINISHED |
| Object | public domain in many jurisdictions |
—
|
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: public domain in many jurisdictions | Statement: [The Arctic Home in the Vedas, publisherStatus, public domain in many jurisdictions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publisherStatus Context triple: [The Arctic Home in the Vedas, publisherStatus, public domain in many jurisdictions]
-
A.
publicationStatus
Indicates the current state or phase of a work within its publication lifecycle, such as draft, under review, published, or retired.
-
B.
publisherType
Indicates the classification or category of a publisher in relation to a published work or entity.
-
C.
hasPublisher
Indicates that an entity is published or issued by a specific publisher.
-
D.
stateOfPublication
Indicates the jurisdiction or territorial state in which a work is formally published or made publicly available.
-
E.
isPublished
Indicates that an item has been formally made available to the public through some publishing process.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af02e65b548190be095df62091b960 |
completed | March 9, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69af018fb0948190a9701b2e8e5d9bac |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af01ee94ec8190aa6dde54d4571c04 |
completed | March 9, 2026, 5:22 p.m. |
Created at: March 9, 2026, 3:45 p.m.