Triple
T9350779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Orpington |
E225011
|
entity |
| Predicate | interactionWithChildren |
P80430
|
FINISHED |
| Object | generally good |
—
|
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: generally good | Statement: [White Orpington, interactionWithChildren, generally good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactionWithChildren Context triple: [White Orpington, interactionWithChildren, generally good]
-
A.
interactionWithHumans
chosen
Indicates a relationship where an entity engages in some form of contact, communication, or mutual influence with humans.
-
B.
childrenWith
Indicates that two or more entities share one or more children together as parents or guardians.
-
C.
sharesChildrenWith
Indicates that two entities are co-parents, having one or more children in common.
-
D.
asksChildrenTo
Indicates that one entity requests or directs children to perform an action or respond in some way.
-
E.
encouragesParentChildEngagement
Indicates that one party promotes or supports active interaction, communication, or shared activities between a parent and child.
- 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4f9248c08190a7bb40feec2eb217 |
completed | April 1, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:41 p.m.