Triple
T23278379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ailanthus altissima |
E588784
|
entity |
| Predicate | urbanEcologyRole |
P8652
|
FINISHED |
| Object | colonizer of vacant urban land |
—
|
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: colonizer of vacant urban land | Statement: [Ailanthus altissima, urbanEcologyRole, colonizer of vacant urban land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanEcologyRole Context triple: [Ailanthus altissima, urbanEcologyRole, colonizer of vacant urban land]
-
A.
ecologicalRoles
Indicates the various functional relationships or roles an entity plays within an ecosystem, such as its contributions to energy flow, nutrient cycling, or species interactions.
-
B.
urbanRole
chosen
Indicates the function, status, or role that an entity holds within an urban or city context.
-
C.
environmentRole
Indicates the functional role or influence that one entity has within or upon a particular environment or environmental context.
-
D.
roleInUrbanPlan
Indicates the specific function, responsibility, or position an entity holds within an urban planning context or scheme.
-
E.
populationRole
Indicates the role or function that an entity has within a population or demographic context.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1957991108190ac82fa6dd355f722 |
completed | April 29, 2026, 5:22 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:49 p.m.