Triple
T29107867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UniParc |
E736814
|
entity |
| Predicate | entryDoesNotContain |
P70649
|
FINISHED |
| Object | functional annotation |
—
|
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: functional annotation | Statement: [UniParc, entryDoesNotContain, functional annotation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: entryDoesNotContain Context triple: [UniParc, entryDoesNotContain, functional annotation]
-
A.
doesNotHave
Indicates that one entity lacks, is missing, or is not in possession of another entity or attribute.
-
B.
doesNotEnter
Indicates that one entity refrains from or fails to go into or cross the boundary of another entity or location.
-
C.
doesNotPrimarilyContain
chosen
Indicates that one entity does not have another entity as its main or predominant component, element, or content.
-
D.
hasEntryOn
Indicates that one entity contains or includes an entry, record, or listing about another entity.
-
E.
entryFor
Indicates that one entity serves as the specific record, representation, or listing corresponding to another entity.
- 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f661bb81b481909690f8617a84cb19 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:16 a.m.