Triple
T31239273
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpha |
E796511
|
entity |
| Predicate | usesConstructedLanguage |
P191804
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alpha, usesConstructedLanguage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesConstructedLanguage Context triple: [Alpha, usesConstructedLanguage, yes]
-
A.
usesNonLinearLanguage
Indicates that the subject communicates or expresses ideas using non-linear, non-sequential, or otherwise non-traditionally structured language.
-
B.
usesKunya
Indicates that one entity refers to or identifies another entity by a kunya (a teknonymic nickname, typically based on "father/mother of" someone).
-
C.
usesWorkingLanguagesOf
Indicates that one entity employs or operates using the working languages associated with another entity.
-
D.
isLanguageOf
Indicates that a particular language is used as the official or primary language associated with a given entity (such as a person, document, or region).
-
E.
hasOwnLanguage
Indicates that an entity possesses or uses a distinct language of its own.
- F. None of above. chosen
Provenance (4 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_69f224db69ac81909a370adad6a7ac7c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: April 29, 2026, 9:11 p.m.