Triple
T8910310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muswell Manor |
E212164
|
entity |
| Predicate | hasLongstandingPresence |
P55641
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Muswell Manor, hasLongstandingPresence, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLongstandingPresence Context triple: [Muswell Manor, hasLongstandingPresence, true]
-
A.
isLongStanding
chosen
Indicates that a relationship, condition, or state has existed for a considerable or extended period of time.
-
B.
hasLargePresenceIn
Indicates that an entity maintains a significant or dominant level of activity, influence, or representation within a specified location, domain, or context.
-
C.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
-
D.
historicalPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
E.
periodOfContinuousInhabitation
Indicates a span of time during which a place is continuously inhabited without interruption.
- 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_69ca839255248190b43984294abd92ae |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc65227d008190b13ba162d0b3c9d1 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.