Triple
T38385453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kudüs-i Şerif Mutasarrıflığı |
E899566
|
entity |
| Predicate | directlyAttachedTo |
P960
|
FINISHED |
| Object | Sublime Porte |
—
|
NE NERFINISHED |
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: Sublime Porte | Statement: [Kudüs-i Şerif Mutasarrıflığı, directlyAttachedTo, Sublime Porte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directlyAttachedTo Context triple: [Kudüs-i Şerif Mutasarrıflığı, directlyAttachedTo, Sublime Porte]
-
A.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
B.
permanentlyAttachedSince
Indicates that one entity has been fixed or joined to another in a way intended to be lasting, starting from a specific point in time.
-
C.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
D.
tiedTo
Indicates that one entity is physically or figuratively fastened, bound, or otherwise constrained in connection to another entity.
-
E.
annexedBy
chosen
Indicates that one entity has been incorporated into and brought under the control or sovereignty of 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_69f76e5c9b808190b486523f5c2f817d |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe9b0276d48190b554fa22b043e6d8 |
completed | May 9, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69fe999692b081909921e1148d66f0ef |
completed | May 9, 2026, 2:19 a.m. |
Created at: May 3, 2026, 4:31 p.m.