Triple

T24076243
Position Surface form Disambiguated ID Type / Status
Subject Treaty of Tripoli (English version, 1797) E596367 entity
Predicate hasOriginalVersionIn P24987 FINISHED
Object Arabic 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: Arabic | Statement: [Treaty of Tripoli (English version, 1797), hasOriginalVersionIn, Arabic]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasOriginalVersionIn
Context triple: [Treaty of Tripoli (English version, 1797), hasOriginalVersionIn, Arabic]
  • A. hasOriginalVersion
    Indicates that one entity is the original or initial version from which another entity is derived or adapted.
  • B. hasVersionIn chosen
    Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
  • C. originalVersionRecordedBy
    Indicates that the original version of a work (e.g., a song or recording) was recorded by a specific performer or recording entity.
  • D. labelForOriginalVersion
    Indicates that something serves as the label or name assigned specifically to the original version of another entity.
  • E. hasEarlierVersion
    Indicates that one entity is an earlier or prior version of another entity in a version sequence.
  • 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_69e288c3999c8190809b282a04813dec completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1db1dd874819087120b06b90be485 completed April 29, 2026, 10:19 a.m.
PD Predicate disambiguation batch_69f1764b1d4c8190b12590c6339c31c1 completed April 29, 2026, 3:08 a.m.
Created at: April 17, 2026, 10:42 p.m.