Triple
T37951545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Acre |
E946756
|
entity |
| Predicate | knownInCrusaderSourcesAs |
P168596
|
FINISHED |
| Object | Acre |
—
|
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: Acre | Statement: [Port of Acre, knownInCrusaderSourcesAs, Acre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownInCrusaderSourcesAs Context triple: [Port of Acre, knownInCrusaderSourcesAs, Acre]
-
A.
roleAtCrusaders
Indicates the specific position, function, or capacity an entity holds within the Crusaders organization or group.
-
B.
knownInHistoryAs
chosen
Indicates that an entity is recognized or referred to by a particular name or title in historical records or accounts.
-
C.
knownInIslamAs
Indicates that an entity is referred to by a particular name, title, or designation specifically within the context of Islam or Islamic tradition.
-
D.
notableCrusade
Indicates that an entity is significantly associated with, or distinguished for its involvement in, a particular Crusade.
-
E.
crusaderHistory
Indicates that an entity has a historical involvement, role, or association with the Crusades or crusading activities.
- 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_69f76ef64cf08190ad3e1114b62aac67 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:20 p.m.