Triple
T27612002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1497 |
E700348
|
entity |
| Predicate | usesMagicCookie |
P170972
|
FINISHED |
| Object | 99.130.83.99 |
—
|
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: 99.130.83.99 | Statement: [RFC 1497, usesMagicCookie, 99.130.83.99]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMagicCookie Context triple: [RFC 1497, usesMagicCookie, 99.130.83.99]
-
A.
usesMagicFor
Indicates that one entity employs or applies magic as a means to achieve, affect, or perform something involving another entity or context.
-
B.
usesMagic
Indicates that an entity performs actions or achieves effects by employing magical powers or supernatural abilities.
-
C.
hasMagicUsers
Indicates that an entity possesses, includes, or is associated with one or more users who can perform or use magic.
-
D.
hasAccessToMagic
Indicates that one entity is able to use, interact with, or benefit from magical powers, resources, or abilities associated with another entity or source.
-
E.
associatedWithMagicUser
Indicates a relationship in which an entity has a connection or involvement with a magic user, such as collaboration, affiliation, or influence.
- 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_69ef6a4f1d9c8190b0705acda054368d |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6984bb55c8190862eb8796868d188 |
completed | May 3, 2026, 12:35 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
| PDg | Predicate description generation | batch_69f6978ec27c8190a488e1f9c2566d38 |
completed | May 3, 2026, 12:32 a.m. |
Created at: April 27, 2026, 2:11 p.m.