Triple
T25999243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Çarşı |
E646573
|
entity |
| Predicate | facedLegalAction |
P3010
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Çarşı, facedLegalAction, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facedLegalAction Context triple: [Çarşı, facedLegalAction, yes]
-
A.
legalActionFiled
Indicates that a formal legal proceeding or complaint has been officially initiated with the appropriate authority or court.
-
B.
allegedAction
Indicates that an action is claimed or asserted to have occurred, typically without being proven or confirmed.
-
C.
hasLegalProceeding
chosen
Indicates that there is a formal legal action, case, or proceeding involving the related entities.
-
D.
facesLegalPersecutionFor
Indicates that one entity is subject to legal charges, prosecution, or punitive legal actions as a consequence of another entity or specified reason.
-
E.
legalActionReason
Indicates the reason, cause, or grounds for which a particular legal action is initiated or taken.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605720be48190b1b64ecdccfaec17 |
completed | May 2, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69f5aff889988190ad10bcf1a280f717 |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 22, 2026, 8:58 a.m.