Triple
T26759850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs. Fairfax |
E674769
|
entity |
| Predicate | welcomesAs |
P161204
|
FINISHED |
| Object | Governess |
—
|
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: Governess | Statement: [Mrs. Fairfax, welcomesAs, Governess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: welcomesAs Context triple: [Mrs. Fairfax, welcomesAs, Governess]
-
A.
welcomesNewMembers
Indicates that an entity actively receives and accepts new members into its group, organization, or community.
-
B.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
C.
welcomeOfferType
Indicates the type or category of a welcome offer provided in the context of an initial interaction or onboarding.
-
D.
openingGreetingFrom
Indicates that one entity initiates an interaction by sending or expressing an initial greeting to another entity.
-
E.
meetsAs
Indicates that two entities encounter or come together at the same place and time, typically in a planned or recognized interaction.
- F. None of above. chosen
Provenance (4 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_69eecda6e9dc81908452fab3ba17ed9b |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f618dafb6c8190b4f53a7fcbf967e3 |
completed | May 2, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
| PDg | Predicate description generation | batch_69f6106d346c8190868489f36c65b6ec |
completed | May 2, 2026, 2:55 p.m. |
Created at: April 27, 2026, 3:57 a.m.