Triple
T11005719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Greek Catholic Church |
E260112
|
entity |
| Predicate | majorLanguageUsed |
P58450
|
FINISHED |
| Object | Romanian |
—
|
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: Romanian | Statement: [Romanian Greek Catholic Church, majorLanguageUsed, Romanian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorLanguageUsed Context triple: [Romanian Greek Catholic Church, majorLanguageUsed, Romanian]
-
A.
languagesUsed
chosen
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
B.
languageOfPrimaryProgramming
Indicates the programming language that is primarily used to implement or develop a given entity.
-
C.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
D.
programmingLanguageUsage
Indicates that an entity uses, is implemented in, or otherwise employs a particular programming language.
-
E.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.