Triple
T4532515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Harran (1104) |
E106329
|
entity |
| Predicate | hasPrisoners |
P57303
|
FINISHED |
| Object | many Crusader nobles captured |
—
|
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: many Crusader nobles captured | Statement: [Battle of Harran (1104), hasPrisoners, many Crusader nobles captured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrisoners Context triple: [Battle of Harran (1104), hasPrisoners, many Crusader nobles captured]
-
A.
hasPrison
Indicates that one entity possesses, contains, or is the location of a prison associated with another entity.
-
B.
hasPrisonerPopulation
Indicates that an entity maintains or contains a population of prisoners, specifying the number or presence of incarcerated individuals associated with it.
-
C.
hasNotableCategoryOfPrisoners
Indicates that a prison is known for housing a specific, notable category or type of prisoners.
-
D.
inmates
Indicates that one entity is confined or held as a prisoner within an institution or facility associated with another entity.
-
E.
hasBeenImprisonedBy
Indicates that one entity has been confined or incarcerated under the authority or control of another entity.
- F. None of above. chosen
Provenance (4 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_69bd43f3d6e08190a91824f833d51bbe |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd579f27ac8190ae9a4252109e56e1 |
completed | March 20, 2026, 2:20 p.m. |
| PD | Predicate disambiguation | batch_69bd521edd00819099dfccaa65dddd61 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:03 p.m.