Triple
T35471535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ace of Spades |
E1025219
|
entity |
| Predicate | classAssociation |
P183327
|
FINISHED |
| Object | Hunter |
—
|
NE NERFINISHED |
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: Hunter | Statement: [Ace of Spades, classAssociation, Hunter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classAssociation Context triple: [Ace of Spades, classAssociation, Hunter]
-
A.
functionAssociation
Indicates that one entity is associated with, implements, or is linked to a particular function or functional role of another entity.
-
B.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
C.
doctrineAssociation
Indicates an association or connection between entities based on a shared doctrine, belief system, or set of principles.
-
D.
antAssociation
Indicates a relationship in which one entity is associated or interacts in a specific, notable way with ants.
-
E.
testAssociation
Indicates that one entity is linked to another through a testing-related relationship, such as participation in, subject of, or responsibility for a test.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79da8d8848190ab5ab1bdad95d58c |
completed | May 3, 2026, 7:10 p.m. |
Created at: May 3, 2026, 4:04 p.m.