Triple

T25569807
Position Surface form Disambiguated ID Type / Status
Subject kings of Byblos E640941 entity
Predicate hasPart P35 FINISHED
Object Ahiram of Byblos
Ahiram of Byblos was an ancient Phoenician king best known from his elaborately inscribed sarcophagus, which bears one of the earliest significant examples of the Phoenician alphabet.
E1690644 NE 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: Ahiram of Byblos | Statement: [kings of Byblos, hasPart, Ahiram of Byblos]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Ahiram of Byblos
Triple: [kings of Byblos, hasPart, Ahiram of Byblos]
Generated description
Ahiram of Byblos was an ancient Phoenician king best known from his elaborately inscribed sarcophagus, which bears one of the earliest significant examples of the Phoenician alphabet.

Provenance (5 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_69e75dc281bc819095ec04dc0c3a94d0 completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f5f8fedd38819096b4cb0016019b7d completed May 2, 2026, 1:15 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10c131a73c8190988bd4ad38b2246e completed May 22, 2026, 8:48 p.m.
NEDg Description generation batch_6a10c2eee95481908b782308c2a2e5cc completed May 22, 2026, 8:56 p.m.
NED2 Entity disambiguation (via description) batch_6a10c365b12c8190bc9b683ad855c776 completed May 22, 2026, 8:58 p.m.
Created at: April 21, 2026, 3:56 p.m.