Triple
T17107675
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | باي تونس |
E415142
|
entity |
| Predicate | سابقًا |
P122422
|
FINISHED |
| Object | حاكم تابع للسلطان العثماني |
—
|
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: حاكم تابع للسلطان العثماني | Statement: [باي تونس, سابقًا, حاكم تابع للسلطان العثماني]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: سابقًا Context triple: [باي تونس, سابقًا, حاكم تابع للسلطان العثماني]
-
A.
previouslyIn
chosen
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
-
B.
wasPrecededBy
Indicates that one event, state, or entity occurred or existed earlier in time than another.
-
C.
previouslyBasedOn
Indicates that something was formerly derived from, adapted from, or dependent on another source, but is no longer based on it in its current state.
-
D.
usedToBe
Indicates that something held a particular state, role, or property in the past but no longer does in the present.
-
E.
usedInPastBy
Indicates that an entity was previously utilized or employed by another entity at some time in the past.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc280b0c8190b9e620b90e0d4b40 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.