Triple
T34545465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabana Podragu |
E886912
|
entity |
| Predicate | languageUsedByStaff |
P101585
|
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: [Cabana Podragu, languageUsedByStaff, Romanian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageUsedByStaff Context triple: [Cabana Podragu, languageUsedByStaff, Romanian]
-
A.
languageUsedAs
Indicates that one language is employed in a specific role, function, or context relative to another entity or situation.
-
B.
languageOfMembers
chosen
Indicates that the specified language is used or spoken by the members of a given group or organization.
-
C.
languagesUsed
Indicates that one entity uses, employs, or is expressed in one or more languages associated with the other entity.
-
D.
languagesSpoken
Indicates that an entity is able to communicate using one or more specified languages.
-
E.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a007338002081908cb6340d65ff86d5 |
completed | May 10, 2026, 11:59 a.m. |
| PD | Predicate disambiguation | batch_6a0072a137ac8190a7debeb28e738e03 |
completed | May 10, 2026, 11:57 a.m. |
Created at: May 1, 2026, 2:02 a.m.