Triple
T18180712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Long Lost Family |
E435271
|
entity |
| Predicate | typicalCaseType |
P10545
|
FINISHED |
| Object | adoptees seeking birth parents |
—
|
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: adoptees seeking birth parents | Statement: [Long Lost Family, typicalCaseType, adoptees seeking birth parents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCaseType Context triple: [Long Lost Family, typicalCaseType, adoptees seeking birth parents]
-
A.
typicalCaseTypes
chosen
Indicates the kinds or categories of cases that are most commonly associated with or handled by a given entity.
-
B.
typicalCaseCaptionFormat
Indicates the standard or commonly used way of formatting the caption (title block) of a legal case or similar proceeding.
-
C.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
D.
typicalCoreType
Indicates that something is a standard or characteristic core type within a given classification or system.
-
E.
caseTypes
Indicates the types or categories of cases associated with or applicable to an entity or situation.
- 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_69d8b90c7ec081909b4694ccecb449c6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dffa75a081908dad0dcbd736172d |
completed | April 19, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.