Triple
T24308865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Article 18 of the Anti-Dumping Agreement |
E612609
|
entity |
| Predicate | authenticTextIn |
P155511
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Article 18 of the Anti-Dumping Agreement, authenticTextIn, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticTextIn Context triple: [Article 18 of the Anti-Dumping Agreement, authenticTextIn, English]
-
A.
followsInText
Indicates that one textual element appears immediately or subsequently after another within the same text.
-
B.
usesTextBy
Indicates that one entity makes use of or relies on a text authored or provided by another entity.
-
C.
textBy
Indicates that a given text or written content was authored or produced by a particular entity.
-
D.
allowsText
Indicates that one entity permits or supports the use, input, or display of textual content in relation to another entity.
-
E.
hasFictionalSignText
Indicates that an entity bears or is associated with text appearing on a fictional sign (e.g., wording depicted on an in-universe sign).
- 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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29228ede48190b05c85320f373155 |
completed | April 29, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69f1c45c6ec081908401b69424428100 |
completed | April 29, 2026, 8:42 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 1:32 a.m.