Triple

T35729503
Position Surface form Disambiguated ID Type / Status
Subject Trencavel family E1032713 entity
Predicate ruled P760 FINISHED
Object Viscounty of Nîmes
The Viscounty of Nîmes was a medieval feudal lordship in southern France, historically associated with the influential Trencavel dynasty and the wider politics of Languedoc.
E2157818 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: Viscounty of Nîmes | Statement: [Trencavel family, ruled, Viscounty of Nîmes]
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: Viscounty of Nîmes
Triple: [Trencavel family, ruled, Viscounty of Nîmes]
Generated description
The Viscounty of Nîmes was a medieval feudal lordship in southern France, historically associated with the influential Trencavel dynasty and the wider politics of Languedoc.

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_69f76e10e59081908d81ad9ce22f40b6 completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f7a13384bc8190b721f871f8602496 completed May 3, 2026, 7:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a38a4d5d1248190a780bc1dd48daf17 completed June 22, 2026, 2:58 a.m.
NEDg Description generation batch_6a38a5be38a88190a389bb6a60b2d33b completed June 22, 2026, 3:02 a.m.
NED2 Entity disambiguation (via description) batch_6a38a61805e081909aab709bf28025ef completed June 22, 2026, 3:03 a.m.
Created at: May 3, 2026, 4:05 p.m.