Triple
T23357779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conde |
E593095
|
entity |
| Predicate | hasCognateTitle |
P2525
|
FINISHED |
| Object | Count (English) |
—
|
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: Count (English) | Statement: [Conde, hasCognateTitle, Count (English)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCognateTitle Context triple: [Conde, hasCognateTitle, Count (English)]
-
A.
hasCognate
chosen
Indicates that two linguistic forms in different languages share a common historical origin, typically descending from the same ancestral word.
-
B.
hasLatinTitleOf
Indicates that one entity has, uses, or is associated with the Latin-language title corresponding to another entity.
-
C.
equivalentOrRelatedTitle
Indicates that two titles are the same or sufficiently similar in meaning, role, or status to be treated as equivalent or closely related.
-
D.
haveAlternativeTitle
Indicates that an entity is known by one or more alternative titles or names in addition to its primary title.
-
E.
hasTitleNamesake
Indicates that one entity serves as the namesake or source of the title borne by another entity.
- 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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19a196b308190bfe9bb4b6e7ec363 |
completed | April 29, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:28 p.m.