Triple
T34305197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andre Boulos |
E880286
|
entity |
| Predicate | hasFamilyReputationIn |
P131437
|
FINISHED |
| Object | business |
—
|
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: business | Statement: [Andre Boulos, hasFamilyReputationIn, business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyReputationIn Context triple: [Andre Boulos, hasFamilyReputationIn, business]
-
A.
hasFamilyReputation
chosen
Indicates that an entity is associated with a particular standing, status, or reputation held by their family.
-
B.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
C.
hasFamilialTieTo
Indicates a relationship where two entities are connected by family bonds, such as by blood, marriage, or adoption.
-
D.
hasFamilyTrait
Indicates that a particular trait or characteristic is shared among members of the same family or lineage.
-
E.
hasReputationAmong
Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 1, 2026, 1:57 a.m.