Triple
T37141775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Trees of North America |
E920131
|
entity |
| Predicate | fieldUsability |
P7231
|
FINISHED |
| Object | portable |
—
|
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: portable | Statement: [Common Trees of North America, fieldUsability, portable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldUsability Context triple: [Common Trees of North America, fieldUsability, portable]
-
A.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
B.
fieldQuality
chosen
Indicates the assessed level or degree of quality associated with a particular field or attribute in a given context.
-
C.
fieldEstablished
Indicates that a particular field, area, or domain has been formally created, set up, or brought into existence at a specific time or by a specific agent.
-
D.
fieldIdentification
Indicates the association of an entity with a specific field, category, or domain used to distinguish or classify it within a broader context.
-
E.
fieldOfPlay
Indicates the spatial area or surface where an activity, event, or interaction takes place.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:15 p.m.