Triple
T38702878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 九条家 |
E950186
|
entity |
| Predicate | courtRankTradition |
P191552
|
FINISHED |
| Object | 摂政・関白を出す家柄 |
—
|
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: 摂政・関白を出す家柄 | Statement: [九条家, courtRankTradition, 摂政・関白を出す家柄]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtRankTradition Context triple: [九条家, courtRankTradition, 摂政・関白を出す家柄]
-
A.
courtRank
Indicates the formal hierarchical rank or status an individual holds within a court or courtly system.
-
B.
courtRankBeforeAccession
Indicates the formal court rank or position a person held prior to their accession to a higher office or title.
-
C.
hierarchyInLegalSystem
Indicates that one legal authority, norm, or institution holds a higher or lower rank relative to another within a structured legal system.
-
D.
legalHierarchyRank
Indicates the relative position or level of authority an entity holds within a legal or judicial hierarchy.
-
E.
traditionalCourt
Indicates that an entity is associated with or takes place in a conventional or historically established court of law, as opposed to a modern, alternative, or informal judicial setting.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdfbafbf48190abe38ec0003a6419 |
completed | May 7, 2026, 6:53 p.m. |
Created at: May 3, 2026, 4:33 p.m.