Triple
T32240169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trent family |
E823590
|
entity |
| Predicate | closeFriendsWith |
P96345
|
FINISHED |
| Object | Philip Mannering |
—
|
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: Philip Mannering | Statement: [Trent family, closeFriendsWith, Philip Mannering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeFriendsWith Context triple: [Trent family, closeFriendsWith, Philip Mannering]
-
A.
closeRelationship
Indicates a strong, intimate, or emotionally significant bond between two entities, suggesting familiarity, trust, and frequent or meaningful interaction.
-
B.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
-
C.
acquaintanceOf
Indicates that one entity knows another in a casual or non-intimate way, without implying close friendship or strong personal ties.
-
D.
bestFriendDynamicWith
chosen
Indicates a close, primary friendship relationship between two entities, typically characterized by mutual trust, support, and frequent positive interaction.
-
E.
socialCircle
Indicates that one entity belongs to, or is part of, the group of people with whom another entity regularly interacts socially.
- 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_69f3490c140481908ed53b98b561eaa1 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 12:40 a.m.