Triple
T25679222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Brian Young |
E643890
|
entity |
| Predicate | fullLegalName |
P158987
|
FINISHED |
| Object | Michael Brian Young |
—
|
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: Michael Brian Young | Statement: [Michael Brian Young, fullLegalName, Michael Brian Young]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fullLegalName Context triple: [Michael Brian Young, fullLegalName, Michael Brian Young]
-
A.
fullCaseName
Indicates that one entity is the complete, formal name of a legal case associated with another entity.
-
B.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
-
C.
LAUFullName
Indicates that the predicate specifies the complete, official name associated with a given entity.
-
D.
fullNameRevealed
Indicates that an entity’s complete personal name has been disclosed or made known to another party or in a given context.
-
E.
typicalFullName
Indicates that the object is the standard or commonly used full name associated with the subject.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb77c3a08190b63e811dd21989fd |
completed | May 2, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 7:44 p.m.