Triple
T949417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Meadows |
E20485
|
entity |
| Predicate | hasBusinessBackgroundIn |
P17879
|
FINISHED |
| Object | real estate |
—
|
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: real estate | Statement: [Mark Meadows, hasBusinessBackgroundIn, real estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessBackgroundIn Context triple: [Mark Meadows, hasBusinessBackgroundIn, real estate]
-
A.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
B.
hasWorkedIn
chosen
Indicates that a person has been employed or has performed work within a particular organization, location, or domain for some period of time.
-
C.
hasFamilyBackgroundIn
Indicates that an entity comes from, or is associated with, a particular familial or ancestral background.
-
D.
hasBackground
Indicates that an entity possesses or is associated with a particular background, such as context, setting, or prior circumstances.
-
E.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
- 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_69a493b0f2fc81908cd227480a5356a1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3c191ac819099ebf3cb32f096d8 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29f05f481908814bd11f235e9d0 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.