Triple
T26228338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha Elauf |
E655958
|
entity |
| Predicate | appliedForPositionAt |
P60907
|
FINISHED |
| Object | Abercrombie & Fitch |
—
|
NE NERFINISHED |
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: Abercrombie & Fitch | Statement: [Samantha Elauf, appliedForPositionAt, Abercrombie & Fitch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedForPositionAt Context triple: [Samantha Elauf, appliedForPositionAt, Abercrombie & Fitch]
-
A.
appliedFor
chosen
Indicates that an entity has submitted a request or application to another entity for a position, service, benefit, or opportunity.
-
B.
appliesToPosition
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable to a specific position or role.
-
C.
previouslyAppliedTo
Indicates that an entity has submitted an application to another entity at some earlier time in the past.
-
D.
appliesAt
Indicates that an action, rule, or condition is relevant to or in effect at a specific location, context, or point in time.
-
E.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
- 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 26, 2026, 8:58 p.m.