Triple
T28285793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun Kuang |
E713275
|
entity |
| Predicate | youngerSiblingPosition |
P50641
|
FINISHED |
| Object | younger brother |
—
|
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: younger brother | Statement: [Sun Kuang, youngerSiblingPosition, younger brother]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: youngerSiblingPosition Context triple: [Sun Kuang, youngerSiblingPosition, younger brother]
-
A.
youngerSibling
Indicates that one entity is the younger sibling of another in a family or sibling relationship.
-
B.
siblingPositionHeld
chosen
Indicates the specific ordinal position an individual holds among their siblings within a family or sibling group.
-
C.
youngerBrotherRank
Indicates that one entity holds the position or status of a younger brother relative to another entity.
-
D.
positionInFamilyBirthOrder
Indicates the relative order in which a person was born within their family (e.g., first-born, middle child, last-born).
-
E.
youngestBrotherRank
Indicates the ordinal position or rank of an entity among its youngest brothers within a family or sibling group.
- 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6447f85248190b71fc247d284971d |
completed | May 2, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:26 p.m.