Triple
T33478084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucas Lodge |
E857380
|
entity |
| Predicate | relativeStatusTo |
P131864
|
FINISHED |
| Object | less grand than Rosings Park |
—
|
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: less grand than Rosings Park | Statement: [Lucas Lodge, relativeStatusTo, less grand than Rosings Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeStatusTo Context triple: [Lucas Lodge, relativeStatusTo, less grand than Rosings Park]
-
A.
statusRelativeTo
chosen
Indicates the comparative state or condition of one entity in relation to another at a given point or over a period of time.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
-
D.
stateOfRelations
Indicates the current nature or condition of the relationship between two or more entities, such as whether it is friendly, hostile, neutral, or otherwise characterized.
-
E.
relationshipToState
Indicates a relationship or connection that an entity has with a particular state or governmental body.
- 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_69f3497472508190b300ebd3fd402367 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:38 a.m.