Triple
T20189352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nacho |
E492941
|
entity |
| Predicate | hasUsageRegister |
P139041
|
FINISHED |
| Object | informal |
—
|
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: informal | Statement: [Nacho, hasUsageRegister, informal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUsageRegister Context triple: [Nacho, hasUsageRegister, informal]
-
A.
hasRegister
Indicates that one entity possesses, contains, or is associated with a specific register (such as a record, log, or hardware register).
-
B.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
C.
hasUsageLevel
Indicates the degree or intensity with which something is used or utilized.
-
D.
hasUsageNote
Indicates that there is an associated explanatory note describing how or when something should be used.
-
E.
hasRegistrar
Indicates that an entity is formally recorded or overseen by a specific registrar organization or authority.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ad404508190981cfb7cab18d8d3 |
completed | April 20, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69e55b11124c8190babacf2a0fe2d057 |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:37 p.m.