Triple
T5162674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polblue Swamp |
E116472
|
entity |
| Predicate | hasSurroundingTreeCommonName |
P61869
|
FINISHED |
| Object | snow gum |
—
|
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: snow gum | Statement: [Polblue Swamp, hasSurroundingTreeCommonName, snow gum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurroundingTreeCommonName Context triple: [Polblue Swamp, hasSurroundingTreeCommonName, snow gum]
-
A.
hasTree
Indicates that one entity possesses, contains, or is associated with a tree.
-
B.
isNamedTree
Indicates that the entity is a tree that has been given a specific name or designation.
-
C.
hasNearbyForestType
Indicates that one entity is located close to, or in the vicinity of, a forest of a specified type.
-
D.
belongsToFamilyCommonName
Indicates that an entity is associated with, or classified under, a particular family-level common name.
-
E.
hasNearbyCommon
Indicates that two entities share at least one common element, feature, or connection that is located within a specified nearby distance or vicinity.
- F. None of above. chosen
Provenance (4 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79268ea48190a22d3350babc153c |
completed | March 20, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69bd77b36c008190b91011a9fa52b3d2 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd78d6a1388190804dcf568ca92129 |
completed | March 20, 2026, 4:41 p.m. |
Created at: March 20, 2026, 1:44 p.m.