Triple
T35244267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilyon HaShas |
E1017614
|
entity |
| Predicate | scholarlyStyle |
P182654
|
FINISHED |
| Object | concise |
—
|
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: concise | Statement: [Gilyon HaShas, scholarlyStyle, concise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyStyle Context triple: [Gilyon HaShas, scholarlyStyle, concise]
-
A.
scholarlyEmphasis
Indicates a relationship where an entity focuses its academic attention, research, or analysis predominantly on a particular subject, theme, or area of study.
-
B.
scholarlyMilieu
Indicates the intellectual or academic environment, context, or community within which a scholarly work, activity, or figure is situated.
-
C.
scholarlyUse
Indicates that something is used for academic, educational, or research-related purposes.
-
D.
scholarlyWork
Indicates a relationship where an entity is a formal academic or research work produced, published, or recognized within a scholarly context.
-
E.
scholarlyView
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7904a770481908ef3f788e51e8dba |
completed | May 3, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69f78f629d508190b755848162c4e101 |
completed | May 3, 2026, 6:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.