Triple
T1343653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Glen Fault |
E28520
|
entity |
| Predicate | currentActivity |
P19466
|
FINISHED |
| Object | largely inactive |
—
|
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: largely inactive | Statement: [Great Glen Fault, currentActivity, largely inactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentActivity Context triple: [Great Glen Fault, currentActivity, largely inactive]
-
A.
mainCurrentAct
Indicates that an entity is currently performing or engaged in its primary or most important action or activity.
-
B.
currentActivityLevel
chosen
Indicates the present intensity or degree of activity that an entity is engaged in at a given moment.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
activityStartApprox
Indicates that the start time of an activity is known only approximately, rather than as an exact timestamp.
-
E.
activityStartContext
Indicates the circumstances, conditions, or situation present at the moment an activity begins.
- 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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c23b8a9081908b78405d4ef806af |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef3e8fc8190ac9a1ba9b5879483 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.