Triple
T22341535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mountain Girl |
E552284
|
entity |
| Predicate | interactionPattern |
P107806
|
FINISHED |
| Object | meets lone travelers |
—
|
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: meets lone travelers | Statement: [The Mountain Girl, interactionPattern, meets lone travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionPattern Context triple: [The Mountain Girl, interactionPattern, meets lone travelers]
-
A.
typicalInteraction
chosen
Indicates the usual or most common way in which two entities interact or relate to each other.
-
B.
interactionBetween
Indicates a reciprocal or mutual action, influence, or communication occurring between two or more entities.
-
C.
interactionWithHumans
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
D.
interactionMechanism
Indicates the process or means by which one entity affects, influences, or interacts with another.
-
E.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15794fae48190a2b79e9ae4b57bb1 |
completed | April 29, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:43 p.m.