Triple
T18924734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WOAH |
E462944
|
entity |
| Predicate | usesAcronymSince |
P59337
|
FINISHED |
| Object | WOAH since 2022 |
—
|
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: WOAH since 2022 | Statement: [WOAH, usesAcronymSince, WOAH since 2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAcronymSince Context triple: [WOAH, usesAcronymSince, WOAH since 2022]
-
A.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
B.
hasCommonAcronymUsage
Indicates that two terms share the same commonly used acronym in practice.
-
C.
usesNameSince
chosen
Indicates that an entity has been using a particular name continuously starting from a specified point in time.
-
D.
usedAsNicknameSince
Indicates that one entity has been used as a nickname for another entity starting from a specified point in time.
-
E.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c9b77c188190b2274ef45d538508 |
completed | April 20, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:59 a.m.