Triple
T8486621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Accept-Language |
E200846
|
entity |
| Predicate | allowsWildcard |
P60957
|
FINISHED |
| Object | * |
—
|
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: * | Statement: [Accept-Language, allowsWildcard, *]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsWildcard Context triple: [Accept-Language, allowsWildcard, *]
-
A.
wildCardContext
chosen
Indicates that the relationship or action occurs within a flexible, unspecified, or catch‑all contextual scope rather than a narrowly defined one.
-
B.
wildCardBerth
Indicates that an entity receives a berth or qualification through a wildcard allocation rather than through standard qualification criteria.
-
C.
includesMatch
Indicates that one entity contains or encompasses a particular match or matching instance of another entity.
-
D.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
-
E.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53c4d608190a766c0e919a4b96f |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.