Triple
T88390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Jose |
E1776
|
entity |
| Predicate | originalFunction |
P4098
|
FINISHED |
| Object | farming community |
—
|
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: farming community | Statement: [San Jose, originalFunction, farming community]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalFunction Context triple: [San Jose, originalFunction, farming community]
-
A.
separatedFunctionFrom
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
-
B.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
C.
originalChannel
Indicates the communication channel or medium through which something was first created, sent, or published.
-
D.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
E.
originalNetwork
Indicates that one entity is the original or source network from which another network or derived entity is based or obtained.
- 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_69a24d1a97dc819094e6c021fe9b05a7 |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a2503d304c8190a0034ffa4a38a501 |
completed | Feb. 28, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69a24eb6da2c8190a33d144d219f7abe |
completed | Feb. 28, 2026, 2:11 a.m. |
| PDg | Predicate description generation | batch_69a2503c12808190a3cbb7b171f466f0 |
completed | Feb. 28, 2026, 2:17 a.m. |
Created at: Feb. 28, 2026, 2:07 a.m.