Triple
T32048393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yan clan of the State of Lu |
E818414
|
entity |
| Predicate | roleInLu |
P165140
|
FINISHED |
| Object | participated in political life of Lu |
—
|
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: participated in political life of Lu | Statement: [Yan clan of the State of Lu, roleInLu, participated in political life of Lu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInLu Context triple: [Yan clan of the State of Lu, roleInLu, participated in political life of Lu]
-
A.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
B.
roleWithLAT
Indicates a relationship where an entity holds or is associated with a specific role that is characterized or constrained by a particular location, attribute, or type (LAT).
-
C.
roleOn
chosen
Indicates that an entity holds or performs a specific role or function within another entity, context, or activity.
-
D.
roleAccordingTo
Indicates that an entity holds a particular role or function as defined or interpreted by a specified source or perspective.
-
E.
roleWith
Indicates that one entity holds or performs a particular role in relation to another entity.
- 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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffff262fac8190a26ed0577e1860bd |
completed | May 10, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69fffcad7d7c8190a4ad7bb35e33bb75 |
completed | May 10, 2026, 3:34 a.m. |
Created at: May 1, 2026, 12:20 a.m.