Triple
T25006053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Croup |
E625842
|
entity |
| Predicate | duoType |
P81362
|
FINISHED |
| Object | brains of the pair with Mr. Vandemar |
—
|
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: brains of the pair with Mr. Vandemar | Statement: [Mr. Croup, duoType, brains of the pair with Mr. Vandemar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: duoType Context triple: [Mr. Croup, duoType, brains of the pair with Mr. Vandemar]
-
A.
duoMember
chosen
Indicates that an entity is one of the two participants forming a duo with another entity.
-
B.
dualPair
Indicates that two entities form a dual pair, standing in a mathematically defined dual relationship where each is the dual counterpart of the other.
-
C.
twinType
Indicates that one entity is classified as a specific type or category of twin in relation to another entity.
-
D.
denType
Indicates the specific kind or category of den associated with an entity.
-
E.
associatedWithDuo
Indicates a relationship in which an entity is linked or connected to a specific duo, typically implying involvement, collaboration, or relevance to that pair.
- 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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b113f8c8190ae05102e9c2ae076 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.