Triple
T7775839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Journal of Corporation Law |
E221386
|
entity |
| Predicate | articleTypes |
P6001
|
FINISHED |
| Object | scholarly articles |
—
|
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: scholarly articles | Statement: [Journal of Corporation Law, articleTypes, scholarly articles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: articleTypes Context triple: [Journal of Corporation Law, articleTypes, scholarly articles]
-
A.
articleType
chosen
Indicates the specific category or kind of article associated with an entity.
-
B.
articleIISubject
Indicates that the entity functions as the grammatical subject of a sentence governed by Article II.
-
C.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
D.
articleContent
Indicates that one entity is the textual or media content that makes up the body of another entity, typically an article or document.
-
E.
articleRange
Indicates that one entity specifies the start and end points of a contiguous range of articles that are grouped or referenced together.
- 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_69ca83ebbef881909ac47f789145fef7 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cae7e779ec8190b77296d9c2ac3210 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa488532c819093ac40bba0b3c7ef |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 3:51 p.m.