Triple
T3869957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orations |
E91957
|
entity |
| Predicate | traditionallyCollectedAs |
P51578
|
FINISHED |
| Object | set of numbered orations |
—
|
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: set of numbered orations | Statement: [Orations, traditionallyCollectedAs, set of numbered orations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyCollectedAs Context triple: [Orations, traditionallyCollectedAs, set of numbered orations]
-
A.
fieldOfCollection
Indicates the academic or subject area to which a collection or set of collected items belongs.
-
B.
traditionallyUsedBy
Indicates that something has been customarily or historically used by a particular person, group, or culture over time.
-
C.
collects
Indicates that one entity gathers, accumulates, or brings together one or more other entities into its possession or control.
-
D.
collectedBy
Indicates that one entity has gathered, acquired, or assembled another entity, typically as part of a collection or data-gathering process.
-
E.
collectingArea
Indicates the total surface area over which something (typically a device or system) gathers or receives a substance, signal, or resource.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec533828819080f52dae15fdbecd |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.