Triple
T16662972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garip movement |
E404904
|
entity |
| Predicate | movementRejects |
P438
|
FINISHED |
| Object | traditional Ottoman prosody |
—
|
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: traditional Ottoman prosody | Statement: [Garip movement, movementRejects, traditional Ottoman prosody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movementRejects Context triple: [Garip movement, movementRejects, traditional Ottoman prosody]
-
A.
positionRejected
Indicates that an offered position, role, or job has been declined or not accepted by the relevant party.
-
B.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
C.
rejectedBy
chosen
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
D.
rejectedFromEvent
Indicates that an entity was denied participation in, or access to, a particular event.
-
E.
refusedAction
Indicates that an entity deliberately declined or did not agree to perform a specific action requested, expected, or proposed by another entity.
- 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_69d8838b5fbc81908c6575c132b82e80 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37c99efa8819096c6325ff4898bd7 |
completed | April 18, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.