Triple
T38086450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anping Tree House |
E950987
|
entity |
| Predicate | overgrownBy |
P135455
|
FINISHED |
| Object | banyan trees |
—
|
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: banyan trees | Statement: [Anping Tree House, overgrownBy, banyan trees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overgrownBy Context triple: [Anping Tree House, overgrownBy, banyan trees]
-
A.
grewToOver
Indicates that something increased in size, amount, or level until it surpassed a specified threshold.
-
B.
overarchedBy
chosen
Indicates that one entity is physically or conceptually spanned, covered, or dominated from above by another entity.
-
C.
growsAlong
Indicates that one entity develops or extends in physical proximity and roughly parallel to the length or course of another entity.
-
D.
growsIn
Indicates that one entity develops, thrives, or increases in size or number within a specified environment, medium, or location.
-
E.
isGrowingAs
Indicates that one entity is developing, evolving, or increasing in some capacity in the manner or role specified by another entity.
- 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_69f76f03a3608190a73fd6df87c792a8 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:21 p.m.