Triple
T26994614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judith Mountains |
E679946
|
entity |
| Predicate | hasHumanActivityHistory |
P99136
|
FINISHED |
| Object | prospecting |
—
|
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: prospecting | Statement: [Judith Mountains, hasHumanActivityHistory, prospecting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHumanActivityHistory Context triple: [Judith Mountains, hasHumanActivityHistory, prospecting]
-
A.
hasHistoryIn
chosen
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
B.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
C.
hasEvidenceOfActivitySince
Indicates that there is evidence showing an entity has been active or engaged in some activity from a specified point in time onward.
-
D.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 6:54 a.m.