Triple
T27894311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | nèidān |
E705443
|
entity |
| Predicate | goalIncludes |
P32133
|
FINISHED |
| Object | harmonizing with the Dao |
—
|
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: harmonizing with the Dao | Statement: [nèidān, goalIncludes, harmonizing with the Dao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalIncludes Context triple: [nèidān, goalIncludes, harmonizing with the Dao]
-
A.
goalStatementIncludes
Indicates that a goal statement contains or explicitly mentions a particular element, concept, or condition.
-
B.
objectiveIncludes
chosen
Indicates that a broader objective encompasses or contains a specific sub-objective, component, or element as part of its scope.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
goalAssociatedWith
Indicates that a goal is connected or linked to another entity, such as an activity, plan, or outcome, in a way that reflects relevance or influence.
-
E.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
- 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_69ef96b490ac8190a412d04c5d009f3e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:37 p.m.