Triple
T3867987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunday |
E91907
|
entity |
| Predicate | usedInExpression |
P51567
|
FINISHED |
| Object | Sunday best |
—
|
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: Sunday best | Statement: [Sunday, usedInExpression, Sunday best]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInExpression Context triple: [Sunday, usedInExpression, Sunday best]
-
A.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
B.
usedInArgumentFor
Indicates that something (such as a statement, piece of evidence, or concept) is employed as support within an argument advocating for a particular claim or position.
-
C.
usedInCase
Indicates that something (such as an item, method, or piece of information) is employed or applied within a particular case or instance.
-
D.
usedInOperation
Indicates that something (such as a tool, method, or resource) is employed or applied during the execution of a particular operation or procedure.
-
E.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
- 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_69aeec3cc1a88190924125a86f72fd5b |
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:19 p.m.