Triple
T4021336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Scholar |
E91284
|
entity |
| Predicate | hasOptionalLogin |
P13123
|
FINISHED |
| Object | Google account |
—
|
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: Google account | Statement: [Google Scholar, hasOptionalLogin, Google account]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOptionalLogin Context triple: [Google Scholar, hasOptionalLogin, Google account]
-
A.
hasOptionalSection
Indicates that an entity includes a section or component that is not mandatory and may or may not be present.
-
B.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
-
C.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
D.
hasPass
Indicates that an entity possesses or has been granted a pass, such as a ticket, permit, or authorization to access something.
-
E.
hasOptionalProtocol
chosen
Indicates that an entity may, but is not required to, follow or support a specified protocol.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefacb4c208190b8dd595a534850b2 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8fc78ec819092d4dab88d85a141 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.