Triple
T27774046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berkeley |
E699135
|
entity |
| Predicate | hasHistoricMarketStatus |
P84335
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Berkeley, hasHistoricMarketStatus, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricMarketStatus Context triple: [Berkeley, hasHistoricMarketStatus, true]
-
A.
hasHistoricMarket
chosen
Indicates that an entity possesses or is the location of a market of historical significance.
-
B.
hasMarketStatus
Indicates the current commercial or trading condition of an entity, such as whether it is active, suspended, listed, or delisted in a market.
-
C.
hasMarketCharterStatus
Indicates that an entity holds a specific official market charter status, such as being authorized, licensed, or otherwise formally recognized to operate in a designated market.
-
D.
hasHistoricalData
Indicates that an entity possesses recorded information or records about past events, states, or values relevant to it.
-
E.
hasHistoricalPosition
Indicates that an entity has held a specific role, office, or position during a past historical period.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 27, 2026, 5:04 p.m.