Triple
T35420839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alba |
E1023785
|
entity |
| Predicate | isUnderCareOf |
P182950
|
FINISHED |
| Object | Mickey |
—
|
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: Mickey | Statement: [Alba, isUnderCareOf, Mickey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUnderCareOf Context triple: [Alba, isUnderCareOf, Mickey]
-
A.
adoptedUnder
Indicates that something has been formally accepted, implemented, or brought into effect according to a specified rule, procedure, or authority.
-
B.
transferredUnder
Indicates that something is moved, conveyed, or reassigned from one party, context, or control to another under specified terms or conditions.
-
C.
acceptedOnBehalfOf
Indicates that one party formally accepts something (such as an offer, agreement, or responsibility) while acting as a representative or proxy for another party.
-
D.
residesUnder
Indicates that one entity lives or is situated beneath another entity in a hierarchical or spatial structure.
-
E.
isUnderAdministrationOf
Indicates that one entity is managed, governed, or overseen by another authority or administrative body.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7958b1e2481909227813f382e79a0 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.