Triple
T28931215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blasi |
E733785
|
entity |
| Predicate | sharesLinguisticRootsWith |
P28322
|
FINISHED |
| Object | Blaise |
—
|
NE NERFINISHED |
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: Blaise | Statement: [Blasi, sharesLinguisticRootsWith, Blaise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesLinguisticRootsWith Context triple: [Blasi, sharesLinguisticRootsWith, Blaise]
-
A.
sharesLinguisticFamilyWith
Indicates that two languages belong to the same linguistic family or branch within a language family.
-
B.
linguisticallyRelatedTo
Indicates that two entities are connected through a linguistic relationship, such as sharing a common language, origin, structure, or other language-based association.
-
C.
sharesEtymologyWith
chosen
Indicates that two terms originate from the same linguistic root or source word, or have closely related historical word origins.
-
D.
hasCommonLoanwordsFrom
Indicates that two languages share loanwords that originate from the same source language.
-
E.
commonInLanguageFamily
Indicates that the related items are frequently found or widely used across languages within the same language family.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: April 28, 2026, 8:28 a.m.