Triple
T6161549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I Ching |
E137453
|
entity |
| Predicate | lineTypes |
P15027
|
FINISHED |
| Object | broken 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: broken line | Statement: [I Ching, lineTypes, broken line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineTypes Context triple: [I Ching, lineTypes, broken line]
-
A.
lineType
chosen
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for another entity.
-
C.
railwayLineType
Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
-
D.
lineFamily
Indicates that two entities belong to the same family or lineage associated with a particular line (e.g., a family line or line-based grouping).
-
E.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
- 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_69c008a54fc88190b6ce4416490ca79d |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d371484819090c18b62b095b49e |
completed | March 22, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69c055f5b81481908819515cdc334ae6 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:17 p.m.