Triple
T38231886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAE |
E1013510
|
entity |
| Predicate | hasSpeakingTest |
P199080
|
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: [CAE, hasSpeakingTest, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpeakingTest Context triple: [CAE, hasSpeakingTest, yes]
-
A.
hasSpokenSampleBy
Indicates that an entity has a spoken or audio sample that was produced or performed by a specified agent.
-
B.
hasSpeech
Indicates that an entity produces, delivers, or is associated with a spoken utterance or verbal expression.
-
C.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
hasSpokenStandard
Indicates that an entity has spoken using a recognized standard form of a language (e.g., standard dialect or official register).
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff1d85441c8190931e758685a269f7 |
completed | May 9, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_69ff1d186cc48190b315c61e23de6551 |
completed | May 9, 2026, 11:40 a.m. |
| PDg | Predicate description generation | batch_69ff1d8394988190acf163a07acad200 |
completed | May 9, 2026, 11:41 a.m. |
Created at: May 3, 2026, 4:30 p.m.