Triple
T215485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Highland Boundary Fault |
E4811
|
entity |
| Predicate | trend |
P5318
|
FINISHED |
| Object | southwest–northeast |
—
|
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: southwest–northeast | Statement: [Highland Boundary Fault, trend, southwest–northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trend Context triple: [Highland Boundary Fault, trend, southwest–northeast]
-
A.
hasTrend
chosen
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
technologyTrend
Indicates a relationship where a technology is characterized as part of a broader pattern of change or direction in technological development over time.
-
C.
economicTrend
Indicates the general direction or pattern of economic activity or conditions over a period of time.
-
D.
intellectualTrend
Indicates a relationship where an idea, movement, or way of thinking is recognized as an intellectual trend influencing thought or discourse.
-
E.
popularity
Indicates how widely liked, admired, or favored something or someone is by a group of people.
- 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_69a2575cb1dc8190a01ad332426dc339 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25dcd2b208190855d5d8d70a3acfc |
completed | Feb. 28, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69a25b52190481908f299d26122bafd2 |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:52 a.m.