Triple
T17597622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wang Ming |
E428613
|
entity |
| Predicate | alignmentWithinCCP |
P16437
|
FINISHED |
| Object | pro‑Moscow line |
—
|
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: pro‑Moscow line | Statement: [Wang Ming, alignmentWithinCCP, pro‑Moscow line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alignmentWithinCCP Context triple: [Wang Ming, alignmentWithinCCP, pro‑Moscow line]
-
A.
alignmentComponents
Indicates that one entity is composed of or associated with specific subparts or elements that together form its overall alignment.
-
B.
alignmentConcept
chosen
Indicates a conceptual or abstract relationship of alignment or correspondence between entities, such as agreement, compatibility, or shared orientation in some dimension.
-
C.
alignmentMethod
Indicates the technique or procedure used to align one entity with another or with a reference standard.
-
D.
alignmentShape
Indicates that one entity’s shape is arranged, oriented, or matched in position relative to another entity’s shape.
-
E.
alignmentGoal
Indicates that an entity has a desired or target alignment state it aims to achieve or maintain.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e469ecfb108190a9e7a5b380f8ab93 |
completed | April 19, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.